From: Michael Haggerty <mhagger@alum.mit.edu>
To: Chris Shoemaker <c.shoemaker@cox.net>
Cc: Martin Langhoff <martin.langhoff@gmail.com>,
Julian Phillips <julian@quantumfyre.co.uk>,
git@vger.kernel.org, dev <dev@cvs2svn.tigris.org>
Subject: Re: CVS -> SVN -> Git
Date: Sat, 14 Jul 2007 22:01:31 +0200 [thread overview]
Message-ID: <46992B9B.1070306@alum.mit.edu> (raw)
In-Reply-To: <20070714173223.GA25574@pe.Belkin>
Chris Shoemaker wrote:
> [...] I, for one, would be interested to know how
> cvs2svn's output compared to CVSps's, especially w.r.t. detecting each
> branch's parent.
The problem, as I'm sure you are aware, is that CVS does not record
unambiguously the parent of a branch. For example, the following two
situations are indistinguishable from the data stored in CVS:
1. Create BRANCH1 from trunk, then create BRANCH2 from BRANCH1 before
making any commits to BRANCH1
2. Create BRANCH1 from trunk, then create BRANCH2 from the same trunk
revision.
Older versions of cvs2svn would always create both branches from trunk.
cvs2svn 2.0 gathers statistics about the "possible parents" of each
symbol across multiple files. If BRANCH1 and BRANCH2 occur in another
file in a context that makes it clear that BRANCH2 was created from
BRANCH1 (i.e., because a revision was committed to BRANCH1 before
BRANCH2 was created), then it attempts to use BRANCH1 as the parent of
BRANCH2 in all files.
So yes, cvs2svn is somewhat intelligent about determining the correct
branch ancestry.
Michael
next prev parent reply other threads:[~2007-07-14 20:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 14:48 CVS -> SVN -> Git Julian Phillips
2007-07-13 23:03 ` Michael Haggerty
2007-07-14 5:30 ` Martin Langhoff
2007-07-14 17:09 ` Michael Haggerty
2007-07-14 17:32 ` Chris Shoemaker
2007-07-14 20:01 ` Michael Haggerty [this message]
2007-07-14 18:14 ` Steffen Prohaska
2007-07-15 2:22 ` Shawn O. Pearce
2007-07-14 19:52 ` Eric S. Raymond
2007-07-14 20:58 ` Junio C Hamano
2007-07-14 21:50 ` Oswald Buddenhagen
2007-07-14 22:19 ` Michael Haggerty
2007-07-14 22:44 ` Karl Fogel
2007-07-14 23:23 ` David Frech
2007-07-15 2:30 ` Shawn O. Pearce
2007-07-15 11:48 ` Michael Haggerty
2007-07-16 1:08 ` Martin Langhoff
2007-07-16 1:13 ` Julian Phillips
2007-07-16 1:30 ` Karl Fogel
2007-07-15 1:39 ` Eric S. Raymond
2007-07-15 12:04 ` Michael Haggerty
2007-07-15 13:36 ` Eric S. Raymond
2007-07-16 1:05 ` Martin Langhoff
2007-07-19 12:02 ` Markus Schiltknecht
2007-07-20 3:51 ` Karl Fogel
2007-07-19 19:14 ` Simon 'corecode' Schubert
2007-07-20 8:45 ` Markus Schiltknecht
2007-07-15 23:09 ` Scott Lamb
2007-07-19 19:18 ` Simon 'corecode' Schubert
2007-07-19 19:15 ` Simon 'corecode' Schubert
2007-07-20 5:58 ` Julian Phillips
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46992B9B.1070306@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=c.shoemaker@cox.net \
--cc=dev@cvs2svn.tigris.org \
--cc=git@vger.kernel.org \
--cc=julian@quantumfyre.co.uk \
--cc=martin.langhoff@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).