From: "Shawn O. Pearce" <spearce@spearce.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Nick Andrew <nick@nick-andrew.net>,
git@vger.kernel.org
Subject: Re: Mercurial to git converter.
Date: Sun, 15 Jun 2008 22:24:35 -0400 [thread overview]
Message-ID: <20080616022435.GS11793@spearce.org> (raw)
In-Reply-To: <m3wsksotdq.fsf@localhost.localdomain>
Jakub Narebski <jnareb@gmail.com> wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> > FWIW I switched my local mercurial2git conversion to the hg-fast-export
> > solution from
> >
> > git://repo.or.cz/fast-export.git
> >
> [...]
> > Originally, I did not try it because I thought it cannot operate in
> > incremental mode, but it can.
>
> It can, or it can recently thanks to --export-marks / --import-marks
> work?
The recent --export-marks/import-marks work you speak of was adding
these options to git-fast-export, making it easier to perform an
incremental _export_ from Git to another SCM. I believe Dscho
is speaking about an Hg->Git conversion, which would rely on
git-fast-import's previously existing --export-marks/import-marks
feature.
> It is nice that SCM-to-SCM converters seems to standarize on using
> fast-import language as intermediary.
Turns out the little format we knocked together for this is able
to represent most conversions for SCMs. I'm just happy users are
easily able to convert into Git.
> IIRC fast-import by Shawn O. Pearce started as fast backend for first
> cvs2git (unfortunately fork and not extension of cvs2svn) by Jon Smirl
> (?) around time when Mozilla looked for SCM to move to from CVS. (In
> the end they choose Mercurial, mainly because of better Windows
> support, and I think also better Windows GUI; I wonder how it works
> for them now?).
Your history is correct. The current version of cvs2svn also
supports cvs2git, and may also support cvs2bzr by using the
git-fast-import backend and bzr-fast-import as the parser.
--
Shawn.
next prev parent reply other threads:[~2008-06-16 2:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 17:49 Mercurial to git converter Stelian Pop
2007-01-12 19:28 ` Jakub Narebski
2007-01-12 20:14 ` Stelian Pop
2007-01-12 21:57 ` [PATCH] Add hg-to-git conversion utility Stelian Pop
2007-01-12 22:15 ` Shawn O. Pearce
2007-01-12 23:00 ` Stelian Pop
2007-01-12 23:14 ` Junio C Hamano
2007-01-12 23:18 ` Stelian Pop
2008-06-14 10:23 ` Mercurial to git converter Nick Andrew
2008-06-14 15:53 ` Johannes Schindelin
2008-06-14 16:48 ` Jakub Narebski
2008-06-16 2:24 ` Shawn O. Pearce [this message]
2008-06-16 8:21 ` Nick Andrew
2008-06-16 8:26 ` Mike Hommey
2008-06-17 9:12 ` Johannes Schindelin
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=20080616022435.GS11793@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=nick@nick-andrew.net \
/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).