Re: CVS -> SVN -> Git

On 7/15/07, Eric S. Raymond <esrthyrsus.com> wrote:
> Not quite.  I'm suggesting it's an appropriate lingua
franca for centralized
> VCSes with branching, e.g. everything pre-Arch.

That's a huge goal that gets in the way of waht we want to
do here: we
are trying to save time, not embark on some huge mission.

cvs2svn has all the "wtf-did-cvs-mean-by-that"
algorithms that are
very hard to write and maintain, and it seems to be the best
one at
that. Of course, it also writes SVN repos -- but I'm sure
that's the
easiest part.

     We don't need no meta VCS for any of this.

All we need is to hook into the "write out a repo based
on all the
stuff we parsed from cvs". Perhaps it's doable, and if
Michael helps
out abstracting that part a bit, maintainable long term
too.

cheers,



m

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribecvs2svn.tigris.org
For additional commands, e-mail: dev-helpcvs2svn.tigris.org

Hi,

Martin Langhoff wrote:
> cvs2svn has all the
"wtf-did-cvs-mean-by-that" algorithms that are
> very hard to write and maintain, and it seems to be the
best one at
> that. Of course, it also writes SVN repos -- but I'm
sure that's the
> easiest part.
> 
>     We don't need no meta VCS for any of this.

Sure, we certainly need a meta format of some sort (not a
full blown 
VCS, agreed, but somehow we need to represent commits, tags
and 
branches). And IMO, the subversion based format is not a
good one, 
because it treats branches and tags very different from most
other 
systems (and from what it should be from a users
perspective: an atomic 
operation).

We (Michael, Oswald and me) have discussed joining efforts
of my cvs to 
monotone converter, but I quickly dropped that idea because
the cvs2svn 
converter is too subversion specific. If cvs2svn wants to
become a 
universal cvs importer, it needs to get rid of those
assumptions (and do 
more work to unify tagging and branching).

Regards

Markus


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribecvs2svn.tigris.org
For additional commands, e-mail: dev-helpcvs2svn.tigris.org

[sorry for jumping in so late, didn't read gitvger for
a while]

Martin Langhoff wrote:
> On 7/15/07, Eric S. Raymond <esrthyrsus.com> wrote:
>> Not quite.  I'm suggesting it's an appropriate
lingua franca for 
>> centralized
>> VCSes with branching, e.g. everything pre-Arch.

I do not think Eric is right here.  You will allways lose
information when converting CVS to svn, and if it is just
the uncertainty, the non-atomicity.  This is also
information (hidden one, though).

> That's a huge goal that gets in the way of waht we want
to do here: we
> are trying to save time, not embark on some huge
mission.
> 
> cvs2svn has all the
"wtf-did-cvs-mean-by-that" algorithms that are
> very hard to write and maintain, and it seems to be the
best one at
> that. Of course, it also writes SVN repos -- but I'm
sure that's the
> easiest part.

True.  However, cvs2svn has many assumptions (or at least
has had when I last checked) which are targeted to svn, and
unsuitable for a generic system (tags + branches).

>     We don't need no meta VCS for any of this.

Yes.  I've already done what people want, it is not called
cvs2xxx, but fromcvs [1].  I don't think it is necessary to
define an output format.  Of course, that's possible, but
limiting yourself to a file format means you're losing
flexibility, which is needed for efficient, correct and fast
repository conversion.

cheers
  simon

[1] http://
ww2.fs.ei.tum.de/~corecode/hg/fromcvs/

-- 
Serve - BSD     +++  RENT this banner advert  +++    ASCII
Ribbon   /"
Work - Mac      +++  space for low €€€ NOW!1  +++     
Campaign      /
Party Enjoy Relax   |   http://dragonflybsd.org  
   Against  HTML   
Dude 2c 2 the max   !   http://golden-apple.biz  
    Mail + News   / 

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribecvs2svn.tigris.org
For additional commands, e-mail: dev-helpcvs2svn.tigris.org