From: Junio C Hamano <gitster@pobox•com>
To: Felipe Contreras <felipe.contreras@gmail•com>
Cc: Jeff King <peff@peff•net>, git@vger•kernel.org
Subject: Re: [PATCH] remote-helpers: point at their upstream repositories
Date: Mon, 19 May 2014 21:32:07 -0700 [thread overview]
Message-ID: <xmqq4n0l2hq0.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <537ab8a0d1304_2edfa832fc53@nysa.notmuch> (Felipe Contreras's message of "Mon, 19 May 2014 21:06:24 -0500")
Felipe Contreras <felipe.contreras@gmail•com> writes:
> Junio C Hamano wrote:
>> Junio C Hamano <gitster@pobox•com> writes:
>>
>> > Felipe Contreras <felipe.contreras@gmail•com> writes:
>> >
>> >> We could. Personally I don't see the point of making the warning any
>> >> more annoying....
>>
>> If we were giving the users a choice of "no thanks, I'll keep using
>> the obsolete one", then trying to be a low key and giving them a way
>> to squelch with an advice.* config might make sense, but if we plan
>> to remove/stub at as early as v2.1, I think annoyance is very much
>> what we want, actually, because it clearly is the case that we do
>> prefer users switching instead of waiting for v2.1.
>>
>> How does this sound?
>
> The patch below assumes the user has ~/bin in his PATH, which might not
> be the case. Personally I don't see the point of creating extra
> annoyance with instructions that might not work.
Yeah, I would be lying if I said that "that might not work" did not
bother me, but I decided it would be on the good side of the
borderline (it is better to be concise and slightly wrong than
ultra-verbose and precise). As you may have guessed, they were
stolen from your earlier message that shows what the site says after
all ;-)
I will probably tag -rc4 with the patch applied sometime tomorrow.
next prev parent reply other threads:[~2014-05-20 4:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 22:56 [PATCH] remote-helpers: point at their upstream repositories Junio C Hamano
2014-05-16 7:37 ` Felipe Contreras
2014-05-16 8:41 ` Jeff King
2014-05-16 8:55 ` Paolo Ciarrocchi
2014-05-16 8:59 ` Jeff King
2014-05-16 9:03 ` Felipe Contreras
2014-05-16 9:23 ` Felipe Contreras
2014-05-16 16:52 ` Junio C Hamano
2014-05-16 22:39 ` Felipe Contreras
2014-05-17 2:11 ` James Denholm
2014-05-17 5:24 ` Felipe Contreras
2014-05-18 1:24 ` James Denholm
2014-05-18 2:31 ` Felipe Contreras
2014-05-18 23:05 ` Junio C Hamano
2014-05-19 1:19 ` Felipe Contreras
2014-05-19 21:31 ` Junio C Hamano
2014-05-20 14:55 ` Michael Haggerty
2014-05-20 15:20 ` Johan Herland
2014-05-20 21:31 ` Felipe Contreras
2014-05-20 20:52 ` Felipe Contreras
2014-05-16 22:52 ` Jeff King
2014-05-17 5:25 ` Felipe Contreras
2014-05-17 6:24 ` Jeff King
2014-05-17 17:15 ` Felipe Contreras
2014-05-18 17:34 ` Matthieu Moy
2014-05-18 22:48 ` Felipe Contreras
2014-05-18 23:13 ` Junio C Hamano
2014-05-19 1:31 ` Felipe Contreras
2014-05-19 6:11 ` Junio C Hamano
2014-05-19 21:21 ` Felipe Contreras
2014-05-19 22:27 ` Junio C Hamano
2014-05-19 23:17 ` Junio C Hamano
2014-05-20 2:06 ` Felipe Contreras
2014-05-20 4:32 ` Junio C Hamano [this message]
2014-05-19 19:01 ` Junio C Hamano
2014-05-20 20:39 ` Felipe Contreras
2014-05-20 21:11 ` Junio C Hamano
2014-05-20 21:28 ` Felipe Contreras
2014-05-20 21:50 ` Junio C Hamano
2014-05-16 18:07 ` Junio C Hamano
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=xmqq4n0l2hq0.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=felipe.contreras@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox