Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: Subscriber actions for migrating lists to lists.linux.dev
Date: Fri, 16 Apr 2021 17:16:15 -0400	[thread overview]
Message-ID: <20210416211615.7serx3oa2rloe7al@nitro.local> (raw)
In-Reply-To: <cd77ebe2e456cb80527d9634a5469254006528c5.camel@HansenPartnership.com>

On Fri, Apr 16, 2021 at 01:58:22PM -0700, James Bottomley wrote:
> 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)?

We still add both List-Id and X-Mailing-List headers, but as "List-Id" is an
actual RFC standard, I suggest filtering based on that. E.g. for
linux-staging@lists.linux.dev we add the following headers:

    X-Mailing-List: linux-staging@lists.linux.dev
    List-Id: <linux-staging.lists.linux.dev>
    List-Subscribe: <mailto:linux-staging+subscribe@lists.linux.dev>
    List-Unsubscribe: <mailto:linux-staging+unsubscribe@lists.linux.dev>

> 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.

Note, that once we get around to vger lists, we'll be preserving the address
and list-id without changes. The lists we're currently migrating are moving
from other places -- either from domains we don't control (lists.01.org), or
from domains like lists.linuxfoundation.org where there are MLs that will
likely not enjoy mlmmj-style list management and will move to groups.io
instead after we cherry-pick the devel lists.

-K

  reply	other threads:[~2021-04-16 21:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 20:58 Subscriber actions for migrating lists to lists.linux.dev James Bottomley
2021-04-16 21:16 ` Konstantin Ryabitsev [this message]
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=20210416211615.7serx3oa2rloe7al@nitro.local \
    --to=konstantin@linuxfoundation.org \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox