From: Mike Hommey <mh@glandium.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Mercurial to git converter.
Date: Mon, 16 Jun 2008 10:26:33 +0200 [thread overview]
Message-ID: <20080616082633.GA10752@glandium.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0806141648020.6439@racer>
On Sat, Jun 14, 2008 at 04:53:04PM +0100, Johannes Schindelin wrote:
> Hi,
>
> On Sat, 14 Jun 2008, Nick Andrew wrote:
>
> > Stelian Pop <stelian <at> popies.net> writes:
> >
> > > I switched recently from Mercurial to git for some of my projects, and
> > > needed a conversion tool with branch support (unlike tailor). I didn't
> > > find any, so I ended up writing my own one.
> > >
> > > hg-to-git.py can probably be greatly improved (it's a rather crude
> > > combination of shell and python) but it does already work quite well
> > > for me. [...]
> >
> > Thanks for that. One small problem is that it does not get the changelog
> > right if a commit is made on a local branch. It thinks the "branch:"
> > line is part of the changelog.
>
> FWIW I switched my local mercurial2git conversion to the hg-fast-export
> solution from
>
> git://repo.or.cz/fast-export.git
Would you happen to have a clonable mirror or this ? repo.or.cz doesn't
respond.
Mike
next prev parent reply other threads:[~2008-06-16 8:28 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
2008-06-16 8:21 ` Nick Andrew
2008-06-16 8:26 ` Mike Hommey [this message]
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=20080616082633.GA10752@glandium.org \
--to=mh@glandium.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.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).