From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: users@linux.kernel.org, tools@linux.kernel.org
Subject: Subscriber actions for migrating lists to lists.linux.dev
Date: Fri, 16 Apr 2021 13:58:22 -0700 [thread overview]
Message-ID: <cd77ebe2e456cb80527d9634a5469254006528c5.camel@HansenPartnership.com> (raw)
I'm fairly certain all I need to do is a bit of duplicate message
elimination and to update my procmail rules, but on the latter, what is
the header I should be sorting on? For current kernel.org lists, it's
either X-Mailing-list: or List-ID: Will it be the same for
lists.linux.dev (so I just add to the domain in the rule)?
Ordinarily I'd just wait and see, but given the volumes involved I
wasn't keen on waking up to hundreds of emails suddenly in my INBOX
instead of the list folders.
James
next reply other threads:[~2021-04-16 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-16 20:58 James Bottomley [this message]
2021-04-16 21:16 ` Subscriber actions for migrating lists to lists.linux.dev Konstantin Ryabitsev
2021-04-16 21:22 ` James Bottomley
2021-04-16 21:26 ` Konstantin Ryabitsev
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=cd77ebe2e456cb80527d9634a5469254006528c5.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=tools@linux.kernel.org \
--cc=users@linux.kernel.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.