public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: nunojsilva@ist.utl.pt (Nuno J. Silva)
To: gentoo-user@lists.gentoo.org
Cc: nicolas.s-dev@laposte.net
Subject: [gentoo-user] Re: Mailing list policy on reply
Date: Fri, 02 Jul 2010 11:01:09 +0100	[thread overview]
Message-ID: <87k4petd7e.fsf@ist.utl.pt> (raw)
In-Reply-To: 4C2D5D5D.6010109@gmail.com

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.
>>>
>>> What do you think about changing of policy?

Like others, I'm happy with this as it is. But YMMV.

> When they start a new list and it is not set up this way, it causes
> confusion.  This was discussed before on another list.  I don't see
> this changing anytime soon and hope it doesn't.

Is there a way for someone to add another address to Reply-To? (Does the
list management software overwrite the header or just appends its
address?)

Such a way would suit the OP and people who don't want duplicate
messages at the same time. 

Meanwhile the OP might want to add a request to be CC'ed to his
signature.

-- 
Nuno J. Silva
gopher://sdf-eu.org/1/users/njsg




  reply	other threads:[~2010-07-02 10:01 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 [this message]
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
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=87k4petd7e.fsf@ist.utl.pt \
    --to=nunojsilva@ist.utl.pt \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=nicolas.s-dev@laposte.net \
    /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