[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Best Practice for cvs2svn

From: <kfogel_at_collab.net>
Date: 2006-03-30 02:43:27 CEST

Can this thread happen on users@cvs2svn.tigris.org, not
users@subversion.tigris.org? Thanks.


"James Levinson" <jlevinson@ziprealty.com> writes:
> 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 luck.
> 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.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 30 07:49:02 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.