I think the main use I will have for the history is understanding how the database code works and evolved, since that is where my understanding is weakest. That part of it goes back to about 2001. I really don't want to gave to use SCCS to work with that code! I anticipate that being able to see how changes were made in the past will give me a template for future changes.
The most voluminous part of the history is before then, the pre-database record of registrations. To be honest, that part of it is a bit of a liability: it is full of personal data so it means I can't publish the repository as it is. But now that I have everything in git, it will be much easier to carve out the relevant parts which can be published.
And having it all in git means I can keep it all in one place rather than having to worry about preserving old archives somewhere else. There is a backup/archive on our staff timesharing server which will remain in some form, but my aim is to be able to forget about it :-)
no subject
Date: 2014-11-28 13:07 (UTC)I think the main use I will have for the history is understanding how the database code works and evolved, since that is where my understanding is weakest. That part of it goes back to about 2001. I really don't want to gave to use SCCS to work with that code! I anticipate that being able to see how changes were made in the past will give me a template for future changes.
The most voluminous part of the history is before then, the pre-database record of registrations. To be honest, that part of it is a bit of a liability: it is full of personal data so it means I can't publish the repository as it is. But now that I have everything in git, it will be much easier to carve out the relevant parts which can be published.
And having it all in git means I can keep it all in one place rather than having to worry about preserving old archives somewhere else. There is a backup/archive on our staff timesharing server which will remain in some form, but my aim is to be able to forget about it :-)