From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Robin H. Johnson" <robbat2@gentoo.org>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: parsecvs repository moved...
Date: Mon, 16 Apr 2007 20:51:13 +1200 [thread overview]
Message-ID: <46a038f90704160151q2121086bx1b224804d93ba481@mail.gmail.com> (raw)
In-Reply-To: <20070416084238.GL2689@curie-int.orbis-terrarum.net>
On 4/16/07, Robin H. Johnson <robbat2@gentoo.org> wrote:
> No, it's correct in this case. I have it configured to collapse any
> occurrence of my address into the list address, because I'm subscribed
> to the list, and prefer to not receive duplicates.
OTOH you _are_ breaking the reply / reply-all convention that most
people use and (almost) all MUAs handle correctly.
This means that I have a practical way to address you in private by
just hitting 'reply'. Most mailing-list-adept users will do that to
send you a private reply. It's pretty ackward that you are seeding the
reply-to with bogus addresses. I'd guess it'd bother me less if you
set the reply-to to /dev/null.
If you'd rather not receive duplicates, you can probably filter out
for duplicates in by message-id at your MUA/procmail.
> Gentoo Linux Developer & Council Member
Oh, well. And I thought reply-to flamewars were exclusive to
debian-devel. They are silly enough there.
cheers.
m
next prev parent reply other threads:[~2007-04-16 8:51 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 [this message]
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
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=46a038f90704160151q2121086bx1b224804d93ba481@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--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).