git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: "Robin H. Johnson" <robbat2@gentoo.org>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: parsecvs repository moved...
Date: Mon, 16 Apr 2007 20:59:48 +1200	[thread overview]
Message-ID: <46a038f90704160159j64c6c694xc24b365078ae709a@mail.gmail.com> (raw)
In-Reply-To: <7vbqhovhbk.fsf@assigned-by-dhcp.cox.net>

On 4/16/07, Junio C Hamano <junkio@cox.net> wrote:
> Look at Robin's header again.  It is pointing other people with
> Mail-followup-to: header.

Don't worry -- I did ;-) and I did remember your complaint a few hs ago.

> People do that to avoid getting duplicates from mailing list,
> without realizing how rude that practice is.  It forces people
> who want to address THEM specifically (as opposed to "other
> people") spend extra seconds correcting the e-mail header.

Yeah -- and the fun thing is that you can get caught with a nasty
gaffe if you hit reply and send of what you think is a private
reply... and ends up going to the list.

Mbwa-ha-ha, watch those flamewars start. Not.

Let's use the reply-to as it's meant to be ;-)

cheers,


martin

  reply	other threads:[~2007-04-16  9:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-16  7:32 parsecvs repository moved Martin Langhoff
2007-04-16  7:58 ` Robin H. Johnson
2007-04-16  8:37   ` Martin Langhoff
2007-04-16  8:44     ` Robin H. Johnson
2007-04-16  8:39   ` Martin Langhoff
2007-04-16  8:42     ` Robin H. Johnson
2007-04-16  8:51       ` Martin Langhoff
2007-04-16  8:55         ` Martin Langhoff
2007-04-16 11:48         ` Robin H. Johnson
2007-04-16  8:45     ` Junio C Hamano
2007-04-16  8:59       ` Martin Langhoff [this message]
2007-04-16 11:21 ` James Cloos
2007-04-27 15:15   ` Petr Baudis

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=46a038f90704160159j64c6c694xc24b365078ae709a@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=robbat2@gentoo.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).