Re: [PATCH v1 1/2] Remove 'git archimport'

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: May 9, 2014, 17:52 UTC
Message-ID: <536d15f512afd_a7adc530c31@nysa.notmuch>
In-Reply-To: <xmqqlhuazw2c.fsf@gitster.dls.corp.google.com>

Junio C Hamano wrote:

Show 9 quoted lines

> Eric Wong <normalperson@yhbt.net> writes:
> 
> > Felipe Contreras <felipe.contreras@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 tests.

So let's merge git-remote-hg without tests, that way the build cannot break.

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.

-- 
Felipe Contreras