From: Junio C Hamano <gitster@pobox.com>
To: Martin Langhoff <martin@laptop.org>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Eric Wong <normalperson@yhbt.net>,
Martin Langhoff <martin.langhoff@gmail.com>
Subject: Re: [PATCH v1 1/2] Remove 'git archimport'
Date: Tue, 13 May 2014 11:19:54 -0700 [thread overview]
Message-ID: <xmqq1tvxpmlw.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAAhxitED0iV+Pcird2kZzt3nSnr83+isBDZF2Czmh0LzNzQf8g@mail.gmail.com> (Martin Langhoff's message of "Tue, 13 May 2014 14:01:24 -0400")
Martin Langhoff <martin@laptop.org> writes:
> On Thu, May 8, 2014 at 9:33 PM, Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
>> No updates since 2010, and no tests.
>
> NAK.
>
> IMHO, this is quite unfriendly.
>
> Is this removal based on your opinion, or Junio's position (or
> consensus from maintainers from the list)? If there is a clear
> consensus or direction for old code such as this, please let me know
> (but copy martin.langhoff@gmail.com, not just my very old address!).
>
>> Plus, foreign SCM tools should live out-of-tree anyway.
>
> Says who? Is there consensus on this?
>
> It's generally the privilege of the maintainer -- in this case Junio
> or perhaps Linus -- to take harsh stances like this.
>
> Junio, what's your position?
We may think longer when somebody proposes to add a new thing that
may better live outside our tree (including the contrib/ area) than
we used to, simply because Git is more mature these days and the
ecosystem is there to support successful third-party tools, but
removal of existing subcommands needs to weigh the impact of such a
removal to existing users. "No recent updates" does not say anything
with respect to that---we cannot tell between "The tool is perfect
to fill needs of the users" and "Even though the users are reporting
issues, the area maintainer is not being responsive" by non activity
alone, and we know there weren't many unresponded issues in the
recent past.
"There is no longer any project that still hosts anything worth
salvaging in tla", if such a claim can be substantiated, might be a
valid reason to propose a removal, but I do not think this is such a
proposal.
next prev parent reply other threads:[~2014-05-13 18:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 1:33 [PATCH v1 0/2] Remove foreign SCMs Felipe Contreras
2014-05-09 1:33 ` [PATCH v1 1/2] Remove 'git archimport' Felipe Contreras
2014-05-09 5:50 ` Eric Wong
2014-05-09 7:11 ` Felipe Contreras
2014-05-09 8:15 ` Eric Wong
2014-05-09 8:36 ` Felipe Contreras
2014-05-09 8:59 ` Eric Wong
2014-05-09 9:20 ` Felipe Contreras
2014-05-09 14:54 ` Jeff King
2014-05-09 15:15 ` Felipe Contreras
2014-05-09 16:33 ` Felipe Contreras
2014-05-09 17:44 ` Junio C Hamano
2014-05-09 17:52 ` Felipe Contreras
2014-05-09 18:33 ` Thomas Adam
2014-05-09 19:21 ` Eric Wong
2014-05-09 22:01 ` Felipe Contreras
2014-05-13 18:16 ` Martin Langhoff
2014-05-13 18:01 ` Martin Langhoff
2014-05-13 18:05 ` Felipe Contreras
2014-05-13 18:17 ` Martin Langhoff
2014-05-13 18:25 ` Felipe Contreras
2014-05-13 18:19 ` Junio C Hamano [this message]
2014-05-09 1:33 ` [PATCH v1 2/2] Remove 'git quiltimport' Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq1tvxpmlw.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
--cc=martin@laptop.org \
--cc=normalperson@yhbt.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.