git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Mercurial to git converter.
Date: Fri, 12 Jan 2007 20:28:37 +0100	[thread overview]
Message-ID: <eo8ngk$ja$1@sea.gmane.org> (raw)
In-Reply-To: 1168537766.22649.19.camel@localhost.localdomain

Stelian Pop wrote:

> 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. Features:
>       - supports incremental conversion (keep a git repo in sync 
>         with a hg repository)
>       - supports hg branches
>       - converts hg tags 
> 
> Feel free to use it, improve it or even include it in mainline git (like
> git-svn and friends).

Thanks. Added to
  http://git.or.cz/gitwiki/InterfacesFrontendsAndTools#hg-to-git

(Perhaps you should send it as git patch adding file contrib/hg-to-git.py
or contrib/git-hgimport/hg-to-git.py ?)
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  reply	other threads:[~2007-01-12 19:29 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 [this message]
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
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='eo8ngk$ja$1@sea.gmane.org' \
    --to=jnareb@gmail.com \
    --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).