All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@ubuntu.com>
To: Andrey Borzenkov <arvidjaar@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH 5/7] add imported "FDT" module for flattened device tree operations
Date: Thu, 04 Apr 2013 15:33:28 -0400	[thread overview]
Message-ID: <515DD588.5020804@ubuntu.com> (raw)
In-Reply-To: <20130404231526.65f76aab@opensuse.site>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 4/4/2013 3:15 PM, Andrey Borzenkov wrote:
> Actually list sets Reply-To, so it is not necessary reply-to-list.

Only badly behaved ones do.  This field is for the SENDER to set ( for
instance, if they do not want to get a duplicate reply and have the
reply only to to the mailing list ), not the mailing list.  See
http://www.unicom.com/pw/reply-to-harmful.html.

>> so please use reply-to-all instead.
> And I was so often chastised exactly for using reply-to-all.

Then they were wrong.

> So what do you suggest when one subscriber requests reply-to-list
> and another - reply-to-all?

Always use reply-to-all.  If a subscriber does not want to get a
direct reply, they can simply set the reply-to header to point to the
mailing list and they won't get a duplicate reply, but other people
who want the reply, or messages cross posted to multiple mailing lists
will not be broken.  Alternatively they can set up a filter to notice
when the message has been sent to both them and a mailing list they
subscribe to and delete the duplicate.  Another alternative is offered
by most mailing lists where you can configure it to not send you a
copy of the message if you are already listed in the to or cc.

Any way you do it, the onus is on the person not wanting the duplicate
to avoid it, not on everyone else, especially when doing so causes
some people who should get a copy of the message not to, which is much
more harmful than someone getting a duplicate copy they don't want.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRXdWIAAoJEJrBOlT6nu7543QIAMs3qO2yqDRVVChrUGtv54wt
M2VZx1+fyq3JJB3lvNQ1AfNAzqMFUZFK+rj3ugEdg1dCF0J+16kyMV4XO68wm4eb
k1vHxfrjFxL+6wzMLun5LYTDU1u2NjlYhnTktKxlsMJd6xslB8vC9MwnXrsCe1Xc
QCId4v5+FlM2Gt1kyf2MZzBEJ6CJfvds8i3DEA4GJJNGcylqd5gYLH5vyH9sveIP
mP+ahqdPT1xnKN4q/+TrZtnKwXIRIg/rSVBBNt9Rru4GFwv5zZ5bZyLNyq8ilc13
wR1l6EDB5SHBZp/7Tgk1/ZHBb8S9Wcwu4kK6BeTs+SwkTcIuMA9mN4l4AGI/klc=
=P+7M
-----END PGP SIGNATURE-----


  reply	other threads:[~2013-04-04 20:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-24 17:01 [PATCH 5/7] add imported "FDT" module for flattened device tree operations Leif Lindholm
2013-03-30 16:53 ` Francesco Lavra
2013-04-01  2:16 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-04-01 16:42   ` Francesco Lavra
2013-04-07 21:28     ` Francesco Lavra
2013-04-08 18:14     ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-05-17 11:49     ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-05-19 17:36       ` Francesco Lavra
2013-04-02 20:39 ` Phillip Susi
2013-04-04 18:22   ` Francesco Lavra
2013-04-04 19:02     ` Phillip Susi
2013-04-04 19:15       ` Andrey Borzenkov
2013-04-04 19:33         ` Phillip Susi [this message]
2013-04-04 19:46       ` Francesco Lavra

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=515DD588.5020804@ubuntu.com \
    --to=psusi@ubuntu.com \
    --cc=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.