From: Solar Designer <solar@openwall.com>
To: kernel-hardening@lists.openwall.com
Subject: list name prefix
Date: Mon, 29 Jan 2018 16:21:37 +0100 [thread overview]
Message-ID: <20180129152137.GA21423@openwall.com> (raw)
Hi,
Even though at least per my Twitter poll most people prefer mailing
lists to introduce [list name] prefix into message Subjects:
https://twitter.com/solardiz/status/957692620477779969
I am going to disable this for kernel-hardening on Kees Cook's request.
Kees' rationale is "to avoid making grumpy maintainers even more
grumpy", referring to the annoyance the [kernel-hardening] prefix is
causing to Linux kernel subsystem maintainers receiving messages via
other Linux kernel development lists that kernel-hardening messages are
commonly cross-posted to.
Because of the common cross-posts, kernel-hardening was already
configured differently from other Openwall mailing lists - it didn't set
the Reply-To header to the list. Now it'll also differ in its non-use
of [list name] prefix. I hope we can live with that, even though
personally I found that prefix convenient.
I am posting this primarily in case some of you were filtering by the
[list name] prefix, so that you know why your filters break. If so,
please filter by the List-ID header instead.
Alexander
reply other threads:[~2018-01-29 15:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180129152137.GA21423@openwall.com \
--to=solar@openwall.com \
--cc=kernel-hardening@lists.openwall.com \
/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;
as well as URLs for NNTP newsgroup(s).