From: Markus Schiltknecht <markus@bluegap.ch>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: esr@thyrsus.com, Michael Haggerty <mhagger@alum.mit.edu>,
Julian Phillips <julian@quantumfyre.co.uk>,
git@vger.kernel.org, dev <dev@cvs2svn.tigris.org>
Subject: Re: CVS -> SVN -> Git
Date: Thu, 19 Jul 2007 14:02:07 +0200 [thread overview]
Message-ID: <469F52BF.8050300@bluegap.ch> (raw)
In-Reply-To: <46a038f90707151805j454b57fbvb4d7ed526e1e64ce@mail.gmail.com>
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
next prev parent reply other threads:[~2007-07-19 12:02 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
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 [this message]
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=469F52BF.8050300@bluegap.ch \
--to=markus@bluegap.ch \
--cc=dev@cvs2svn.tigris.org \
--cc=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--cc=julian@quantumfyre.co.uk \
--cc=martin.langhoff@gmail.com \
--cc=mhagger@alum.mit.edu \
/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).