From: Stelian Pop <stelian@popies.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add hg-to-git conversion utility.
Date: Sat, 13 Jan 2007 00:00:56 +0100 [thread overview]
Message-ID: <45A81328.9030109@popies.net> (raw)
In-Reply-To: <20070112221525.GA20956@spearce.org>
Shawn O. Pearce a écrit :
> Stelian Pop <stelian@popies.net> wrote:
>> hg-to-git.py is able to convert a Mercurial repository into a git one,
>> and preserves the branches in the process (unlike tailor)
>
> Cool!
>
> You've already written the converter, but you may want to look at
> using git-fast-import as the backend interface to Git. I think
> your code may come out shorter, be clearer, and will run faster.
[...]
> Post 1.5.0 I'm going to nudge Junio to get gfi added to the main
> git.git repository. (Right now I don't want to distract him from
> the release.)
Rebasing hg-to-git.py on gfi will probably be a very good idea once gfi
is in the tree.
But I wrote this since I had a need for it, and once my repositories
converted to git I'm not sure I'll need it again :) So don't count too
much on me to do this rebasing :)
But who knows, on a cold rainy day...
--
Stelian Pop <stelian@popies.net>
next prev parent reply other threads:[~2007-01-12 23:01 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 [this message]
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
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=45A81328.9030109@popies.net \
--to=stelian@popies.net \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.