From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Mailing list policy on reply
Date: Fri, 2 Jul 2010 14:19:36 +0000 (UTC) [thread overview]
Message-ID: <i0ksho$rcq$1@dough.gmane.org> (raw)
In-Reply-To: 201007021202.41048.alan.mckinnon@gmail.com
On 2010-07-02, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> On Friday 02 July 2010 12:01:09 Nuno J. Silva wrote:
>> Dale <rdalek1967@gmail.com> writes:
>> > Grant Edwards wrote:
>> >> On 2010-07-02, Nicolas Sebrecht<nicolas.s-dev@laposte.net> wrote:
>> >>> I'm often stucked by the current policy in this mailing list changing
>> >>> the 'Reply-To' header to the mailing list address. Most mailing
>> >>> lists I use don't do that.
>> >>>
>> >>> It is usually better and prefer the "answer to all" policy as it
>> >>> permit to be notified of an answer without having to track the whole
>> >>> mailing list.
> Or, he could use a mailer that understands mailing lists, like kmail. There
> are others.
>
> Filter list mail into a folder, and tell the mailer it is for a list.
>
> Decide how you want to reply and press (the composer deals with it correctly):
>
> l - reply to list
> a - reply to all
> R - reply to original sender
> r - reply to whatever seems to be default reply address.
>
> So instead of blindly clicking reply and getting all upset about the
> outcome, just press one key and the mailer obeys YOUR intent.
His intent is to receive direct replies to his posts. I don't see how
his choice of mail client has any impact on that.
> Problem solved.
Not really. The OP's choice of mail client isn't going to change what
happens when people reply to his postings. He wants "reply-to" to
contain his address as well as the list address so that he gets a
direct response and doesn't have to bother to check the mailing list
for replies.
--
Grant Edwards grant.b.edwards Yow! Hey, wait
at a minute!! I want a
gmail.com divorce!! ... you're not
Clint Eastwood!!
next prev parent reply other threads:[~2010-07-02 14:20 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 0:54 [gentoo-user] Mailing list policy on reply Nicolas Sebrecht
2010-07-02 1:20 ` [gentoo-user] " Grant Edwards
2010-07-02 3:30 ` Dale
2010-07-02 10:01 ` Nuno J. Silva
2010-07-02 10:02 ` Alan McKinnon
2010-07-02 10:38 ` Nuno J. Silva
2010-07-02 10:46 ` Dale
2010-07-02 11:00 ` Alan McKinnon
2010-07-02 14:19 ` Grant Edwards [this message]
2010-07-02 21:31 ` Neil Bothwick
2010-07-03 3:09 ` Grant Edwards
2010-07-02 7:53 ` [gentoo-user] " Mihamina Rakotomandimby
2010-07-02 8:07 ` Alan McKinnon
2010-07-02 8:14 ` Neil Bothwick
2010-07-02 9:56 ` Alan McKinnon
2010-07-02 14:35 ` Kevin O'Gorman
2010-07-02 16:30 ` Paul Hartman
2010-07-02 11:47 ` Willie Wong
2010-07-02 14:00 ` Tanstaafl
2010-07-03 10:55 ` Mick
2010-07-03 16:37 ` Mick
2010-07-03 17:09 ` Alan McKinnon
2010-07-03 17:44 ` Mick
2010-07-03 19:34 ` Alan McKinnon
2010-07-04 3:21 ` [gentoo-user] " Grant Edwards
2010-07-04 11:00 ` Alan McKinnon
2010-07-04 9:02 ` [gentoo-user] " Neil Bothwick
2010-07-06 10:38 ` Peter Humphrey
2010-07-06 11:14 ` Alan McKinnon
2010-07-06 19:15 ` Christopher Swift
2010-07-10 13:25 ` luis jure
2010-07-03 19:42 ` Volker Armin Hemmann
2010-07-04 9:03 ` Neil Bothwick
2010-07-04 20:19 ` Tanstaafl
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='i0ksho$rcq$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=gentoo-user@lists.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