From: Michael Haggerty <mhagger@alum.mit.edu>
To: Pierre Habouzit <madcoder@debian.org>,
"Shawn O. Pearce" <spearce@spearce.org>,
Ian Clatworthy <ian.clatworthy@internode.on.net>,
Bazaar <bazaar@lists.canonical.com>,
git@vger.kernel.org
Subject: Re: [Fwd: [ANNOUNCE] bzr-fastimport plugin, yet another Bazaar import option]
Date: Fri, 22 Feb 2008 14:14:58 +0100 [thread overview]
Message-ID: <47BECAD2.7000401@alum.mit.edu> (raw)
In-Reply-To: <20080222113737.GA18581@artemis.madism.org>
Pierre Habouzit wrote:
> On Fri, Feb 22, 2008 at 07:32:28AM +0000, Shawn O. Pearce wrote:
>> Michael Haggerty of cvs2svn has spent a good amount of time creating
>> a git-fast-import backend to cvs2svn. Given that cvs2svn is one of
>> the few tools that can read some of the really strange real world
>> CVS trees its good to be able to leverage that work for other systems
>> (SVN, Git, and now Bazaar).
>
> /me opens bigs ears and eyes: does this mean that we have an
> incremental importer of CVS based on git-fast-import ?
cvs2svn is robust and uses git-fast-import, but it is *not* incremental.
Incremental conversion would be fun but it would be a lot of work to
implement in such a way that it works reliably.
Michael
next prev parent reply other threads:[~2008-02-22 13:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47BE167A.4060005@internode.on.net>
2008-02-22 7:32 ` [Fwd: [ANNOUNCE] bzr-fastimport plugin, yet another Bazaar import option] Shawn O. Pearce
2008-02-22 7:47 ` Ian Clatworthy
2008-02-22 10:36 ` Johannes Schindelin
2008-02-22 10:33 ` Johannes Schindelin
2008-02-22 11:37 ` Pierre Habouzit
2008-02-22 11:47 ` cvs2svn, was " Johannes Schindelin
2008-02-22 13:14 ` Michael Haggerty [this message]
2008-02-22 14:44 ` Aidan Van Dyk
2008-02-22 18:20 ` Pierre Habouzit
2008-02-22 19:25 ` Aidan Van Dyk
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=47BECAD2.7000401@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=bazaar@lists.canonical.com \
--cc=git@vger.kernel.org \
--cc=ian.clatworthy@internode.on.net \
--cc=madcoder@debian.org \
--cc=spearce@spearce.org \
/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).