From: Stuart Longland <stuartl@longlandclan.hopto.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] reply-to munging
Date: Fri, 15 Apr 2005 09:20:02 +1000 [thread overview]
Message-ID: <425EFAA2.4000109@longlandclan.hopto.org> (raw)
In-Reply-To: <1113492200.9616.96.camel@cgianelloni.nuvox.net>
[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]
Chris Gianelloni wrote:
> On Fri, 2005-04-15 at 00:15 +1000, Stuart Longland wrote:
>
>>At the moment, I'm used to just clicking the Reply button to send to the
>>list... however, on most lists that I participate in, Reply-To is left
>>alone, so I'm normally in the habit of clicking Reply-To-All. Seeing as
>>I normally have to consciously think *click Reply, not RTA*, I for one
>>certainly won't miss not having Reply-to-All.
>
>
> Reply-to-All is evil. You should be using Reply-to-List. I know that I
> sure don't need to get the same email both on and off-list. Off-list
> emails should be reserved only for when you explicitly do not want to
> send to the list and only to the original email's author.
Well... someone should tell the Thunderbird people that... I'm still
hunting for the "Reply To List" button, and I've been looking for months.
Actually, some mailing list managers actually are intelligent enough to
not forward on an email if you're CC'ed. (Mailman comes to mind) I
agree, having messages sent in duplicate can be annoying, but its not
that hard to read one and delete the other. ;-)
Besides, normally I filter out the user's email address if I know
they're subscribed.
--
+-------------------------------------------------------------+
| Stuart Longland -oOo- http://stuartl.longlandclan.hopto.org |
| Atomic Linux Project -oOo- http://atomicl.berlios.de |
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
| I haven't lost my mind - it's backed up on a tape somewhere |
+-------------------------------------------------------------+
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-04-14 23:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 8:54 [gentoo-dev] reply-to munging Paul de Vrieze
2005-04-14 9:01 ` Andrea Barisani
2005-04-14 9:06 ` Georgi Georgiev
2005-04-14 9:11 ` Andrea Barisani
2005-04-14 11:18 ` Chris Gianelloni
2005-04-14 13:49 ` Ming Zhao
2005-04-14 14:15 ` Stuart Longland
2005-04-14 15:23 ` Chris Gianelloni
2005-04-14 15:42 ` Ciaran McCreesh
2005-04-14 18:59 ` Chris Gianelloni
2005-04-14 16:32 ` Donnie Berkholz
2005-04-14 17:25 ` Drake Wyrm
2005-04-14 18:11 ` Paul de Vrieze
2005-04-14 19:01 ` Chris Gianelloni
2005-04-15 6:02 ` [gentoo-dev] " Duncan
2005-04-15 6:35 ` [gentoo-dev] " Andrea Barisani
2005-04-15 19:52 ` Donnie Berkholz
2005-04-16 8:59 ` Andrea Barisani
2005-04-16 9:09 ` Donnie Berkholz
2005-04-14 20:10 ` Jason Wever
2005-04-15 0:37 ` Georgi Georgiev
2005-04-17 18:02 ` D. Wokan
2005-04-14 23:20 ` Stuart Longland [this message]
2005-04-15 8:50 ` [gentoo-dev] " Torsten Veller
2005-04-15 11:32 ` [gentoo-dev] " Chris Gianelloni
2005-04-14 12:12 ` Graham Murray
2005-04-14 12:40 ` Ciaran McCreesh
2005-04-14 9:16 ` Spider
2005-04-14 9:11 ` Paul de Vrieze
-- strict thread matches above, loose matches on Subject: below --
2002-05-25 16:31 [gentoo-dev] Reply-To Munging Chad M. Huneycutt
2001-01-08 5:26 [gentoo-dev] reply-to munging drobbins
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=425EFAA2.4000109@longlandclan.hopto.org \
--to=stuartl@longlandclan.hopto.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