Hi, On Wed, 11 Jan 2017 00:35:19 +0000 Jonathan McCrohan <jmccro...@gmail.com> wrote:
Unfortunately upstream [1] [2] is not responsive at the moment. I have noticed another fork [3] which is in significantly better shape when using Mercurial 4.0 (only two tests failing), but this has diverged significantly from the original upstream. As a result, it is not possible to cherry-pick a patch or two which would resolve this issue. Assistance from someone with knowledge of both Git and Mercurial internals would be gratefully accepted. Regards, Jon [1] https://github.com/felipec/git-remote-hg/ [2] https://github.com/fingolfin/git-remote-hg/ [3] https://github.com/mnauw/git-remote-hg/
I am the maintainer/writer of the fork [3] mentioned above, which has indeed evolved quite somewhat from the original upstream to address quite some issues.
More relevant here; I have re-run the tests (of [3]) against (local checkout of) Mercurial 4.0 and Mercurial 4.1 and all tests pass in my setup (not counting harmless known breakages) (?). So is there any more info on the failing ones that would allow resolving things to a clean test sheet?
Also, the compatibility adjustment to Mercurial 4.0 is fairly minor (afaics only 1 commit involving a few lines), so if really desired/preferred that could probably be back-ported to the original upstream. Though again, as said, there are quite some limitations and issues in the original that have been handled in the fork (somewhat regrettably so that way given the circumstances).
Regards, Mark
