in reply to OT : Bad week

<my bad week>

see rkg set up cvs incorrectly.

watch rkg copy directories incorrectly, moving cvs data along too.

observe rkg issue an cvs -update command incorrectly.

marvel as cvs obliterates working code.

hear rkg's yelp of agony.

watch with amazement as rkg stabs mindlessly at cvs try to retrieve working code.

</my bad week>


zakzebrowski, for what it is worth, my suggested method of dealing with bad days to leave work and swim laps until your head clears.

happy ending: of course all the code was in CVS somewhere, buried back a few versions, and rkg was able to get it back, but darn it took too long. so now my (belated) new year's resolution is to read the cvs manual....

Replies are listed 'Best First'.
Re: Re: OT : Bad week
by hardburn (Abbot) on Feb 13, 2004 at 06:33 UTC

    Oh yes, CVS can provide no end to entertaining weirdness. My first use (and first big mistake) with CVS is documented for the world to see here on SourceForge. I managed to accidently upload a chunk of my home directory (including GnuPG keys) before I realized what I had done and shut it off. I then got my first lesson in how well CVS supports deleting files.

    : () { :|:& };:

    Note: All code is untested, unless otherwise stated

      CVS lets you delete but you still have a copy in the Attic.

        But it's a big pain to do the deletion, especially when you have to do it one file at a time and have to put in your SSH password each time (should have gotten my SSH key uploaded to SourceForge, but I was new to SSH at the time, too). And, as you mentioned, it doesn't really delete the file, unless you can get into the guts of the CVS database (which for SourceForge, means taking out a support ticket and waiting). So my old GnuPG secret key ring is there for the world to download (though the first thing I did was revoke the keys).

        : () { :|:& };:

        Note: All code is untested, unless otherwise stated