git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Nikolaus Rath <Nikolaus@rath.org>
Cc: git@vger.kernel.org, Eric Wong <e@80x24.org>
Subject: Re: Most recent revision that contains a string
Date: Tue, 23 Aug 2016 12:36:33 -0700	[thread overview]
Message-ID: <xmqqr39fuvjy.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <871t1ghe5s.fsf@thinkpad.rath.org> (Nikolaus Rath's message of "Mon, 22 Aug 2016 11:06:07 -0700")

Nikolaus Rath <Nikolaus@rath.org> writes:

>> Btw, please don't set these headers on kernel.org lists:
>>
>> 	Mail-Copies-To: never
>> 	Mail-Followup-To: git@vger.kernel.org
>>
>> Like any mail server, vger fails from time-to-time and
>> reply-to-all prevents it from being a single point of failure.
>
> Huh? If the list-server fails only I will receive the message so it's
> still lost for everyone else. But I am more than happy to take this
> little risk if it saves me from the nuisance of getting duplicate
> responses.

On a mailing list, your readers' time is more valuable than yours,
simply because there are a lot more of them.

I am typing this message ONLY because I want to talk to YOU, and I
want your address to be on its To: field, with Eric and the list on
Cc: field.  The recipients can prioritize their incoming messages by
reading what's addressed directly to them first and when they have
leftover time they can read ones that they are CC'ed, but because
you used Mail-Followup-To: I had to correct the headers manually,
which means you stole time from me.  And if I didn't then your
Mail-Followup-to: would have stolen time from the other recipients.

Please don't use it on this list.


      reply	other threads:[~2016-08-23 19:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-20 21:41 Most recent revision that contains a string Nikolaus Rath
2016-08-21  1:30 ` Josh Triplett
2016-08-21  8:13   ` Andreas Schwab
2016-08-21  8:48     ` Josh Triplett
2016-08-21  2:46 ` Eric Wong
2016-08-22 18:06   ` Nikolaus Rath
2016-08-23 19:36     ` Junio C Hamano [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqr39fuvjy.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=Nikolaus@rath.org \
    --cc=e@80x24.org \
    --cc=git@vger.kernel.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).