From: bp@alien8.de (Borislav Petkov)
To: linux-arm-kernel@lists.infradead.org
Subject: About Mail-Followup-To and Mutt [Was: Re: [ARM] Fix kernel compile error: drivers/crypto/ixp4xx_crypto.c]
Date: Thu, 2 Jan 2014 19:33:11 +0100 [thread overview]
Message-ID: <20140102183311.GC8772@nazgul.tnic> (raw)
In-Reply-To: <20140102103522.GH16456@n2100.arm.linux.org.uk>
On Thu, Jan 02, 2014 at 10:35:22AM +0000, Russell King - ARM Linux wrote:
> And how does that stop the problem when someone *else* replies to the
> message with a Mail-Followup-To? FYI, I was hounded off LKML for having
> that header set.
>
> When people have this header set, and people reply to such a message, all
> recipients get moved into the To: header. This makes it impossible on
> high traffic lists for people to prioritise their reading of messages
> according to whether they're in the To: header or just in the Cc: header.
>
> Being in the To: header means that someone is directing the message *AT*
> you and wanting *YOU* to do something with it. Being in the Cc: is more
> "for information" and so takes a lower priority.
Totally agreed.
That MFT thing might've been a good idea at the time but in reality
it causes more problems than it solves, with our usage patterns. I've
started ignoring it and would suggest people simply drop all those
"lists/subsribe" directives in their .muttrc.
Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Gerhard Sittig" <gsi@denx.de>,
"Christian Hohnstaedt" <chohnstaedt@innominate.com>,
"Krzysztof Hałasa" <khalasa@piap.pl>,
lkml <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org,
"Herbert Xu" <herbert@gondor.apana.org.au>
Subject: Re: About Mail-Followup-To and Mutt [Was: Re: [ARM] Fix kernel compile error: drivers/crypto/ixp4xx_crypto.c]
Date: Thu, 2 Jan 2014 19:33:11 +0100 [thread overview]
Message-ID: <20140102183311.GC8772@nazgul.tnic> (raw)
In-Reply-To: <20140102103522.GH16456@n2100.arm.linux.org.uk>
On Thu, Jan 02, 2014 at 10:35:22AM +0000, Russell King - ARM Linux wrote:
> And how does that stop the problem when someone *else* replies to the
> message with a Mail-Followup-To? FYI, I was hounded off LKML for having
> that header set.
>
> When people have this header set, and people reply to such a message, all
> recipients get moved into the To: header. This makes it impossible on
> high traffic lists for people to prioritise their reading of messages
> according to whether they're in the To: header or just in the Cc: header.
>
> Being in the To: header means that someone is directing the message *AT*
> you and wanting *YOU* to do something with it. Being in the Cc: is more
> "for information" and so takes a lower priority.
Totally agreed.
That MFT thing might've been a good idea at the time but in reality
it causes more problems than it solves, with our usage patterns. I've
started ignoring it and would suggest people simply drop all those
"lists/subsribe" directives in their .muttrc.
Thanks.
next prev parent reply other threads:[~2014-01-02 18:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 10:51 [ARM] Fix kernel compile error: drivers/crypto/ixp4xx_crypto.c Krzysztof Hałasa
2013-12-31 10:51 ` Krzysztof Hałasa
2013-12-31 13:48 ` Gerhard Sittig
2013-12-31 13:48 ` Gerhard Sittig
2013-12-31 18:01 ` Randy Dunlap
2013-12-31 18:01 ` Randy Dunlap
2014-01-01 12:37 ` Gerhard Sittig
2014-01-01 12:37 ` Gerhard Sittig
2014-01-01 12:46 ` Russell King - ARM Linux
2014-01-01 12:46 ` Russell King - ARM Linux
2014-01-02 0:25 ` Jason Cooper
2014-01-02 0:25 ` Jason Cooper
2013-12-31 18:14 ` Russell King - ARM Linux
2013-12-31 18:14 ` Russell King - ARM Linux
2014-01-01 12:18 ` Gerhard Sittig
2014-01-01 12:18 ` Gerhard Sittig
2014-01-02 8:42 ` About Mail-Followup-To and Mutt [Was: Re: [ARM] Fix kernel compile error: drivers/crypto/ixp4xx_crypto.c] Uwe Kleine-König
2014-01-02 8:42 ` Uwe Kleine-König
2014-01-02 10:35 ` Russell King - ARM Linux
2014-01-02 10:35 ` Russell King - ARM Linux
2014-01-02 18:33 ` Borislav Petkov [this message]
2014-01-02 18:33 ` Borislav Petkov
2014-01-02 17:51 ` Mark Brown
2014-01-02 17:51 ` Mark Brown
2014-01-01 6:06 ` [ARM] Fix kernel compile error: drivers/crypto/ixp4xx_crypto.c Herbert Xu
2014-01-01 6:06 ` Herbert Xu
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=20140102183311.GC8772@nazgul.tnic \
--to=bp@alien8.de \
--cc=linux-arm-kernel@lists.infradead.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.