From: Jim Ramsay <lack@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gentoo-dev-announce list
Date: Thu, 21 Jun 2007 15:55:37 -0600 [thread overview]
Message-ID: <20070621155537.11ee07c7@sed-192.sedsystems.ca> (raw)
In-Reply-To: <467AEFAD.8010904@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
Mike Doty wrote:
> Jim Ramsay wrote:
> > Mike Doty wrote:
> >> or you could ask infra to work it's magic making any post to
> >> -dev-announce post to -dev as well and set the replt-to address for
> >> -dev-announce to -dev. that way it's all automagic.
> >
> > I hope you meant the List-Post header... unless we would like to
> > have another discussion on the merits/evils of reply-to munging :)
> >
> As an announce list, you're NEVER EVER supposed to reply to the list,
> so reply-to munging in this case is appropriate IMO.
Reply-To is supposed to let you reply to the author, in case they need
to use a different return address than what is in the From header.
Which I grant is very rare for Gentoo developers.
But I do agree with you that if reply-to munging is done it should
indeed point at -dev and never the -announce list.
--
Jim Ramsay
Gentoo/Linux Developer (rox,gkrellm)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-21 22:01 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 21:09 [gentoo-dev] gentoo-dev-announce list Donnie Berkholz
2007-06-21 21:16 ` Mike Doty
2007-06-21 21:33 ` Jim Ramsay
2007-06-21 21:37 ` Mike Doty
2007-06-21 21:55 ` Jim Ramsay [this message]
2007-06-21 22:10 ` Chris Gianelloni
2007-06-21 21:38 ` Joe Peterson
2007-06-22 1:34 ` Kumba
2007-06-22 2:06 ` Seemant Kulleen
2007-06-22 9:24 ` Thomas Raschbacher (Gentoo)
2007-06-22 3:02 ` Daniel Ostrow
2007-06-22 10:59 ` Ferris McCormick
2007-06-22 11:26 ` Wernfried Haas
2007-06-23 8:12 ` Alec Warner
2007-06-24 12:46 ` Vlastimil Babka
-- strict thread matches above, loose matches on Subject: below --
2006-06-25 3:06 Donnie Berkholz
2006-06-25 3:30 ` Lance Albertson
2006-06-25 3:54 ` Marius Mauch
2006-06-25 4:01 ` Lance Albertson
2006-06-26 18:47 ` Chris Gianelloni
2006-06-25 5:35 ` Donnie Berkholz
2006-06-25 3:32 ` Ned Ludd
2006-06-25 5:38 ` Donnie Berkholz
2006-06-26 19:10 ` Chris Gianelloni
2006-06-26 20:10 ` Donnie Berkholz
2006-06-26 23:36 ` Lance Albertson
2006-06-27 11:29 ` Simon Stelling
2006-06-28 1:56 ` Ned Ludd
2006-06-27 11:57 ` Chris Gianelloni
[not found] ` <20060625190022.GE13449@elladan.wh-og.hs-niederrhein.de>
2006-06-25 22:18 ` Donnie Berkholz
2006-06-27 7:32 ` Stuart Herbert
2006-06-27 11:20 ` Enrico Weigelt
2006-06-27 11:29 ` Stuart Herbert
2006-06-27 11:24 ` Simon Stelling
2006-06-27 11:32 ` Stuart Herbert
2006-06-27 16:16 ` Donnie Berkholz
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=20070621155537.11ee07c7@sed-192.sedsystems.ca \
--to=lack@gentoo.org \
--cc=gentoo-dev@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