On 02.04.2013, at 22:09, John Keeping wrote:
> On Tue, Apr 02, 2013 at 01:02:49PM -0600, Felipe Contreras wrote:
>> Here is the next round of patches for remote-hg, some which have been
>> contributed through github.
>> Fortunately it seems to be working for the most part, but there are some
>> considerable issues while pushing branches and tags.
> How does this compare to the current state of gitifyhg? That's built
> on top of this git-remote-hg script but seems to have been more actively
> developed recently.
Several bugs that were fixed in gitifyhg some time ago are now fixed in this
I'll try to list some of remaining differences, mostly (in my biased opinion)
improvements on the gitifyhg side. Note that some of these might be outdated
with felipe's recent changes, i.e. I have not yet had time to review and/or
test them all. So please bear that in mind.
* added many new test cases, sadly still including some xfails. Several of
these (both passing and xfailing) also apply to remote-hg (i.e. the issue is
also present in contrib's remote-hg)
* improved handling of hg user names (remote-hg is not able to deal with some
pathological cases, failing to import commits). Sadly, mercurial allows
arbitrary strings as usernames, git doesn't...
* failed pushes to hg are cleanly rolled back (using mq.strip() from the mq
extension), instead of resulting in inconsistent internal state. This is quite
important in real life, and has bitten me several times with remote-hg (and was
the initial reason why I switched to gitifyhg). A typical way to reproduce this
is to push to a remote repository that has commits not yet in my local clone.
* git notes are used to associate to each git commit the sha1 of the
corresponding hg commit, to help users figure out that mapping
* internally, the marks are using the hg sha1s instead of the hg rev ids. The
latter are not necessarily invariant, and using the sha1s makes it much easier
to recover from semi-broken states.
* Better handling of various hg errors, see e.g. . More work is still needed
there with both tools, though .
* Support for creating hg tags from git (i.e. pushing light git tags to heavy
* The gitifyhg test suite is run after each push on Travis CI against several
git / mercurial combinations .
In particular, unlike all other remote-hg implementations I know, we explicitly
promise (and test) compatibility with a specific range of Mercurial versions
(not just the one the dev happens to have installed right now). This has been a
frequent issue for me with the msysgit remote-hg
* Renaming a gitifyhg remote just works . Doing that with remote-hg triggers
a re-clone of the remote repository (if it works at all, I don't remember).
Sadly, while working on gitifyhg, we discovered various more design problems
(from our perspective, at least) in Mercurial, e.g. the fact that commits are
not necessarily normalized, in the sense that "equivalent" commits (same
author, time, changed files / code) can have different hashs, with some nasty
implications for import. This is potentially problematic because without extra
care, these would be mapped to the same commit on the git side.
Unfortunately, we also stumbled into various problems with the git
remote-helper system. We are currently using the fast-import remote-helper
type, but are encountering more and more of its limitations. This affects
remote-hg and gitifyhg equally, and probably other remote helpers. E.g. "git
push --dry-run" seems to be impossible to support with such a remote-helper
(but then I might be mistaken).
Thing is, for several of these I don't feel quite competent enough to come up
with patches that I could submit here. And in my experience just reporting a
perceived problem with the remote-helper API is not going to trigger a response
here . I guess that's why we stopped reporting them here for now, but if
there is interest I could try to compile an overview.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html