in reply to CVS history woes

Hi,

Talking about the CVS issue I would do the upgrade to SVN when the next release is out, make a release tag and switch to SVN to work on the next pre-release ;-).

You can say: Hei, the history is still on the CVS

See it like a book, there're volumes, I don't think there is a big problem to having a tag that says "Imported from CVS blablabla" as the first revision message for a SVN repository

The other topic on discussion, I would say: DOCUMENT. Yes, document it all, document what would be your decision and why. When someday you get blamed for a wrong decision he made because he didn't listened to what you said, then you have your documents. ;-)

But, if this work is limiting you, and you don't see a way in which your manager will change. Just leave.

Regards,

fmerges at irc.freenode.net

Replies are listed 'Best First'.
Re^2: CVS history woes
by RobPayne (Chaplain) on Jul 29, 2006 at 12:48 UTC
    It is possible to switch to SVN in a way that imports the history from CVS. cvs2svn has several different options for how you import the CVS repository.

      Hi,

      Yeah sure, but sometimes people prefer to keep the things as they are.

      Last time I read about this tool it has some caveat, cool to see that it's now doing what it should do :-)

      Regards,

      fmerges at irc.freenode.net