git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: git <git@vger.kernel.org>
Subject: Re: Suprising error message from "git clone"
Date: Mon, 20 Aug 2007 14:25:40 -0700	[thread overview]
Message-ID: <7v8x85sxt7.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <vpqy7g5zz7h.fsf@bauges.imag.fr> (Matthieu Moy's message of "Mon, 20 Aug 2007 23:13:38 +0200")

Matthieu Moy <Matthieu.Moy@imag.fr> writes:

> Junio C Hamano <gitster@pobox.com> writes:
>
>> Untested but something like this should suffice...
>
> Jest tested, it works fine.

Thanks.

>> By the way, could you possibly drop Mail-Followup-To: please?
>
> Err, what's the problem with it? I don't wish to receive duplicate,
> and I ask your mailer not to do so. I don't care too much if the
> header is not honnored, but what you have to do is just to followup
> without bothering about it.

For example, your response had this:

    Mail-Followup-To: Junio C Hamano <gitster@pobox.com>,
	    git <git@vger.kernel.org>

Suppose somebody else who read your message on the git list has
something to say to _YOU_.  Maybe he is pointing out some of the
problems in _your_ thinking.  He may not mind me hearing what he
tells you, but he is primarily talking to you.

Although in practice I tend to pay attention to whatever is said
on the git mailing list, I certainly do not want _my_ address on
the To: header of such a response.  He wants to talk to _you_,
not me, and I process mails addressed "To: " me, and then only
when I have enough time to do so move on to other messages.

You either (1) stole time from me by forcing his message
addressed "To: " me, or (2) if the person who responded to your
message were kind and careful enough to "fix" the header so that
the message is addressed to you and demoting me to the Cc: list,
then you stole time from him.

With (1) you are being rude against me, and with (2) you are
being rude against whoever responds to you.

Please don't.

Filtering duplicates on the receiving end in your mailbox should
not be too much of a hassle, either.

      reply	other threads:[~2007-08-20 21:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20 14:45 Suprising error message from "git clone" Matthieu Moy
2007-08-20 20:40 ` Junio C Hamano
2007-08-20 21:13   ` Matthieu Moy
2007-08-20 21:25     ` 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

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

  git send-email \
    --in-reply-to=7v8x85sxt7.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Matthieu.Moy@imag.fr \
    --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.
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 NNTP newsgroup(s).