From: T Ziomek <ctz001@email.mot.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] REJECT: Too many recipients to the message
Date: Mon, 1 Jun 2009 15:32:59 -0500 [thread overview]
Message-ID: <20090601203258.GG8553@email.mot.com> (raw)
In-Reply-To: <20090601200012.D8869832E416@gemini.denx.de>
On Mon, Jun 01, 2009 at 10:00:12PM +0200, Wolfgang Denk wrote:
> Dear Scott Wood,
>
> In message <4A242071.1010806@freescale.com> you wrote:
> >
> > > there is an increasing number of postings with loooooong lists of
> > > recipients (10 addresses and more); usually several of these are
> > > regular and active users of this mailing list so this is actually
> > > redundant;
> >
> > It is not redundant -- including a person in the CC list brings the mail
> > to their attention faster (and with less chances of missing it) than if
> > they have to pick it out of the list.
>
> An email message is a message is a message, isn't it? The message on
> the list and the Cc: are identical, aren't they?
Yes, but how one's MUA / mail client handles them may *not* be identi-
cal.
Quite a few people configure their MUA to prioritize messages based on
whether they are on the To: list, CC:, BCC:, or none of the above (i.e.
by list membership).
> What is the difference whether you receive one or two identical copies
> of a message?
It's a hassle and distraction to deal with duplicates.
> > How about reconfiguring the list software instead?
>
> I see no reason for that yet.
+1 for not restricting the # of addressees absent a reason other than
"some of them are often redundant".
Tom
--
A: Because it breaks the logical |
flow of the message. | Email to user 'CTZ001'
| at 'email.mot.com'
Q: Why is top posting frowned upon? |
next prev parent reply other threads:[~2009-06-01 20:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 17:58 [U-Boot] REJECT: Too many recipients to the message Wolfgang Denk
2009-06-01 18:39 ` Scott Wood
2009-06-01 18:47 ` Jerry Van Baren
2009-06-01 18:50 ` Scott Wood
2009-06-01 20:01 ` Wolfgang Denk
2009-06-01 20:00 ` Wolfgang Denk
2009-06-01 20:32 ` T Ziomek [this message]
2009-06-01 20:51 ` Wolfgang Denk
2009-06-01 21:08 ` T Ziomek
2009-06-01 22:00 ` Wolfgang Denk
2009-06-01 22:27 ` Scott Wood
2009-06-02 0:09 ` T Ziomek
2009-06-02 6:53 ` Stefan Roese
-- strict thread matches above, loose matches on Subject: below --
2009-06-02 2:52 HeungJun, Kim
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=20090601203258.GG8553@email.mot.com \
--to=ctz001@email.mot.com \
--cc=u-boot@lists.denx.de \
/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