Recently Junio said he was willing to hear the opinion of other people
regarding the move from contrib to the core. This move is already
under way, but suddenly Junio changed his mind.
I have repeatedly asked him to clarify what argument changed his mind,
but he hasn't done so. Hopefully he will do that in this thread, but
I'll jump ahead and assume it's this one by John Keeping:
I do not want to end up in a situation where an update to Git is
blocked by a distribution because git-remote-hg is not updated to
support newer versions of Mercurial sufficiently quickly; this
previously happened in Gentoo due to git-svn and meant that was stuck
on 1.7.8 until 1.7.13 was released [X].
Now, I feel I addressed this argument at length, specially in this
thread , but I'll try to provide a summary of the strongest arguments
1) We can make the tests optional, say 't/optional'. So if they don't
pass, the build of Git is not broken. Additionally, distributions
might prefer to run test-essential if they don't want to run these
2) There's already continuous integration builds to make sure all
the possible incoming changes in Mercurial are detected early on.
3) There has been a *single* case where a new Mercurial (3.0) broke
things. This is due to the fact of how I implemented certain
functionality due to limitations in Mercurial's API. Mercurial
authors can be contacted to improve the API and minimize the
possibility of it happening again.
Given these arguments, I don't see how moving git-remote-hg to the core
could possibly cause any problems, and I don't understand why Junio
would think otherwise. Even if such a breakage causes a problem to the
whole Git, it would make sense to demote these tools *when* such a
problem comes (which I argue it won't). Does it make sense to you that
you get thrown in jail for a crime you haven't committed merely because
someone thinks it's likely you will?
Given the huge amount of work I've put in these remote helpers, and the
fact that Junio said since day 1 he wanted these in the core (and I
was operating under that assumption), I think the demotion back to the
contrib area (and therefore out-of-tree) should be made carefully, and
not from one day to he next as it happened.
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