Jakub Narebski <jnareb@gmail.com> wrote:
quoted text
> 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.
 
quoted text
> 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.

quoted text
> 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html