All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Janzen <pcj@xenomai.sez.to>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Xenomai 3.0-rc3 Interruption on Arietta G25 (AT91SAM9G25 chip)
Date: Thu, 26 Mar 2015 12:32:24 -0700	[thread overview]
Message-ID: <oqegobzh9z.fsf@merlin.sez.to> (raw)
In-Reply-To: <20150326185807.GA15125@hermes.click-hack.org> (Gilles Chanteperdrix's message of "Thu, 26 Mar 2015 19:58:07 +0100")

Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> writes:
>> I'm simply suggesting that xenomai mailman be configured to include
>> this header. Then people would have to consciously edit header fields
>> to send to your private account only.
>
> No, the mailman documentation recommends against that, it is a
> recipe for sending private mails to the list unintentionally, which
> is way worse than the opposite.

Your responses to those who make the trivial mistake of clicking on
"reply" rather than "reply all" seem to indicate that you believe
otherwise.

The rationale behind the mailman developers' stance against Reply-To:
is that users should be encouraged to choose either to reply to the
original sender's personal address, or to the entire list.  This is
the opposite of the stated policy of the xenomai list.

If you personally do not want replies sent only to your personal
address, then feel free to configure your MUA to insert your own
Reply-To: header.  If you want to maximize the amount of
xenomai-related traffic captured in the digests, configure mailman to
do it.

-- Paul



  reply	other threads:[~2015-03-26 19:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 11:07 [Xenomai] Xenomai 3.0-rc3 Interruption on Arietta G25 (AT91SAM9G25 chip) Tianchi Huang
2015-03-23 22:09 ` Gilles Chanteperdrix
2015-03-24 15:55   ` Tianchi Huang
2015-03-24 16:01     ` Gilles Chanteperdrix
2015-03-24 16:13       ` Gilles Chanteperdrix
2015-03-25  8:58         ` Tianchi Huang
     [not found]           ` <CAJT0owE7vtJDWM289=4cNR_LuUqPWAO60nvg9D0NiTQWeN9Xbg@mail.gmail.com>
2015-03-26 14:31             ` Gilles Chanteperdrix
2015-03-26 14:52               ` Tianchi Huang
2015-03-26 14:54                 ` Gilles Chanteperdrix
2015-03-26 15:19                   ` Tianchi Huang
2015-03-26 15:40                   ` Tianchi Huang
2015-03-26 15:44                     ` Gilles Chanteperdrix
2015-03-26 15:58                       ` Tianchi Huang
2015-03-26 16:00                         ` Gilles Chanteperdrix
2015-03-26 16:26                           ` Tianchi Huang
2015-03-26 16:35                             ` Gilles Chanteperdrix
2015-03-26 16:40                               ` Gilles Chanteperdrix
2015-03-26 16:56                               ` Tianchi Huang
2015-03-26 16:57                                 ` Gilles Chanteperdrix
2015-03-26 17:25                                   ` Tianchi Huang
2015-03-26 14:32             ` Gilles Chanteperdrix
2015-03-26 17:08               ` Paul Janzen
2015-03-26 18:30                 ` Gilles Chanteperdrix
2015-03-26 18:51                   ` Paul Janzen
2015-03-26 18:58                     ` Gilles Chanteperdrix
2015-03-26 19:32                       ` Paul Janzen [this message]
2015-03-26 19:52                         ` Gilles Chanteperdrix

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=oqegobzh9z.fsf@merlin.sez.to \
    --to=pcj@xenomai.sez.to \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=xenomai@xenomai.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.