[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: James Levinson <jlevinson_at_ziprealty.com>
Date: 2006-03-30 08:29:29 CEST

Thanks for the input Blair & Res...i'll check that forum, but it is an
svn question despite the subject. I have cvs2svn working just fine,
along with svn 1.3 & https through apache 2.2 (on RHE). I was just
looking for some advice on how to implement the migration in real life.
I'll go with the weekend big bang theory.

-----Original Message-----
From: kfogel [mailto:kfogel@collab.net]
Sent: Wednesday, March 29, 2006 4:43 PM
To: James Levinson
Cc: users@subversion.tigris.org
Subject: Re: Best Practice for cvs2svn

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

-Karl

"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 08:31:40 2006

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