Junio C Hamano wrote:
> Eric Wong <normalper...@yhbt.net> writes:
> > Felipe Contreras <felipe.contre...@gmail.com> wrote:
> >> No updates since 2010, and no tests.
> > Who benefits from this removal? Is this causing a maintenance
> > burden for Junio?
> No. See http://thread.gmane.org/gmane.comp.version-control.git/248587
This has nothing to do with that thread.
This is a *CORE* tool, not part of contrib.
Core tools should have tests, shouldn't they?
In a previous thread you were worried that git-remote-hg might break
things because the Mercurial interface could change and break tests
(which WON'T HAPPEN). And here we have a tool which doesn't even have
So let's merge git-remote-hg without tests, that way the build cannot
If an actively maintained, production-ready, well tested, and actively
used tool cannot get into the core, why is an unmaintained, no tested at
all, not actively used tool in the core?
And BTW, the argument John Keeping used for git-remote-hg doesn't apply
to git-remote-bzr where the API doesn't change at all.
Such incredible double standards.
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