Generalizations
Sep. 7th, 2007 06:20 pmSo this morning, after I finally got the first version of the background file check in code checked in to our version control system (apparently with no further disasters), I talked to the guy in charge of our group and said, "How about I take an extra half-day on the project and turn this into a generalized background process handler for our app?"
He thought it was a good idea and so I have.
Unfortunately, someone seems to have changed something somewhere in the build, because I'm not building. So it's time to (slowly) update my local node and see where I end up.
*sigh*
But it'll be nice when it's all done... :)
Update: And an hour later, I'm still trying to complete the check in of all the files.
ClearCase: The World's Slowest Version Control SystemTM
He thought it was a good idea and so I have.
Unfortunately, someone seems to have changed something somewhere in the build, because I'm not building. So it's time to (slowly) update my local node and see where I end up.
*sigh*
But it'll be nice when it's all done... :)
Update: And an hour later, I'm still trying to complete the check in of all the files.
ClearCase: The World's Slowest Version Control SystemTM
no subject
Date: 2007-09-08 12:33 am (UTC)The windows interface does tend to slow it down a bit, but I don't think anything was worse than using sccs at 300 baud.
no subject
Date: 2007-09-08 12:56 am (UTC)And I'm now at 1.5 hours and counting.
With one file that won't check in, because the VOB appears to have disowned it between this afternoon when I checked it out and now.
no subject
Date: 2007-09-08 03:26 am (UTC)I don't seem to have your shipping address.
no subject
Date: 2007-09-08 04:21 am (UTC)no subject
Date: 2007-09-08 04:26 am (UTC)I'm used to systems where five seconds per file is slow for anything under a couple of MB. (Checking in a couple of GB of audio can still take a while, even with git.)
no subject
Date: 2007-09-08 04:29 pm (UTC)I remember leaving a check-in running over a weekend once.