Error trying to convert local CVS repositories
Brian Wallis
brian.wallis at infomedix.com.au
Thu Apr 10 00:59:51 UTC 2008
On 10/04/2008, at 12:54 AM, Hans Meine wrote:
>
> I have recently started working with Mercurial and I am very happy
> with it.
> So far, I have always converted cvs to svn and svn to hg; I trust
> cvs2svn much
> more in making sense out of a cvs repository than cvsps. (Think
> not only of
> multi-file commits, but of moves, copies and direct modifications
> of the cvs
> repository, which were not uncommon operations with CVS..)
>
> However, I think using the convert extension to directly convert a
> CVS repo
> would have the advantage of allowing to convert "live" CVS
> repositories, i.e.
> merge changes done to the CVS repo after the initial convert?
> Also, I am not
> sure if there is any other information (beside the CVS revisions/
> identities)
> that gets lost by my intermediate step.
I have had similar problems and have abandoned use of "hg convert" in
favour of using Tailor due mainly to its support of using either
cvsps *or* just cvs. For our creaky old CVS repository cvsps just
doesn't work for reasons similar to what you describe above.
Tailor can do an initial convert and then run periodic updates to
keep the mercurial repo in sync with changes to the cvs repo. See my
earlier messages "How to organize a 'central repository'" which have
some of my config and scripts attached.
Tailor is working well for us.
Brian Wallis
InfoMedix
p: 3 8615 4553 | f: 3 8615 4501 | e: brian.wallis at infomedix.com.au
Level 5, 451 Little Bourke Street, Melbourne VIC 3000
More information about the Mercurial
mailing list