You win some, you lose some
Feb. 9th, 2005 01:37 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
kickahaWork is going well for the most part. I now have nested templated class declarations working properly, even when the templates are distinct in parameterization and partially specialized. *twitch* Good day on that front.
Until I try and check it in to CVS tonight and get a permissions error on the history file. The data is in the repository, and the logs are correct, but the checkins aren't in the history file. Annoying. Somehow $CVSROOT/history got set to user-writable only, and that user isn't me, but my advisor. Grrr.
So I just spent the last little bit figuring out that the 4200f1c3 in the previous record for this file was actually a hexadecimal format count of the epoch seconds (since Jan 1, 1970), and figured out what the two missing records should be, calculating the new date/time for each. In the morning I'll go bug him to fix the permissions, then I can fix the file, then I can continue checking in.
Don't you just LOVE computers!?!?
*sigh*
This is so not the sort of thing I wanted to deal with right before being done, y'know? I already had one catastrophic data loss, I don't need another one.
Until I try and check it in to CVS tonight and get a permissions error on the history file. The data is in the repository, and the logs are correct, but the checkins aren't in the history file. Annoying. Somehow $CVSROOT/history got set to user-writable only, and that user isn't me, but my advisor. Grrr.
So I just spent the last little bit figuring out that the 4200f1c3 in the previous record for this file was actually a hexadecimal format count of the epoch seconds (since Jan 1, 1970), and figured out what the two missing records should be, calculating the new date/time for each. In the morning I'll go bug him to fix the permissions, then I can fix the file, then I can continue checking in.
Don't you just LOVE computers!?!?
*sigh*
This is so not the sort of thing I wanted to deal with right before being done, y'know? I already had one catastrophic data loss, I don't need another one.