It's really better if you declare a freeze time on a weekend for developers
to stop using cvs then tarball it, follow the cvs2svn instruction and have
your uses to login to the new svn box on Monday. Otherwise, if they
continue checking in code into cvs, you'll have a chicken & egg syndrome on
----Original Message Follows----
From: "James Levinson" <firstname.lastname@example.org>
Subject: Best Practice for cvs2svn
Date: Wed, 29 Mar 2006 14:35:54 -0800
Received: from tigris.org ([22.214.171.124]) by bay0-mc2-f1.bay0.hotmail.com
with Microsoft SMTPSVC(6.0.3790.1830); Wed, 29 Mar 2006 14:37:23 -0800
Received: (qmail 14761 invoked by uid 5000); 29 Mar 2006 22:37:17 -0000
Received: (qmail 14752 invoked from network); 29 Mar 2006 22:37:17 -0000
Mailing-List: contact email@example.com; run by ezmlm
Delivered-To: mailing list firstname.lastname@example.org
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Thread-Topic: Best Practice for cvs2svn
X-OriginalArrivalTime: 29 Mar 2006 22:37:23.0362 (UTC)
I am doing a cvs2svn conversion and I was hoping NOT to shutoff cvs, but
let people migrate at their own pace...
Thus, I have been trying to write a cvs hook script that would commit to
svn. My logic was this: Commit to cvs Repos ---> Update cvs Working dir
---> Copy file to svn Working Dir ---> Commit to svn Repos.
I was trying to do this all in a perl script called from the cvs loginfo
hook. The problem is locking when I fire off the cvs update and I can't
seem to get around it. I tried forking it into the background but no
Anybody ever try to do this ? Should I abandon and just do a big-bang
migration of my dev team. Or is there another way? Any advice much
appreciated ? Thanks.
Donít just search. Find. Check out the new MSN Search!
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Mar 30 07:06:27 2006