Linux maintainer tooling and workflows
 help / color / Atom feed
* Subscriber actions for migrating lists to lists.linux.dev
@ 2021-04-16 20:58 James Bottomley
  2021-04-16 21:16 ` Konstantin Ryabitsev
  0 siblings, 1 reply; 4+ messages in thread
From: James Bottomley @ 2021-04-16 20:58 UTC (permalink / raw)
  To: users, tools

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



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Subscriber actions for migrating lists to lists.linux.dev
  2021-04-16 20:58 Subscriber actions for migrating lists to lists.linux.dev James Bottomley
@ 2021-04-16 21:16 ` Konstantin Ryabitsev
  2021-04-16 21:22   ` James Bottomley
  0 siblings, 1 reply; 4+ messages in thread
From: Konstantin Ryabitsev @ 2021-04-16 21:16 UTC (permalink / raw)
  To: James Bottomley; +Cc: users, tools

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Subscriber actions for migrating lists to lists.linux.dev
  2021-04-16 21:16 ` Konstantin Ryabitsev
@ 2021-04-16 21:22   ` James Bottomley
  2021-04-16 21:26     ` Konstantin Ryabitsev
  0 siblings, 1 reply; 4+ messages in thread
From: James Bottomley @ 2021-04-16 21:22 UTC (permalink / raw)
  To: Konstantin Ryabitsev; +Cc: users, tools

On Fri, 2021-04-16 at 17:16 -0400, Konstantin Ryabitsev wrote:
> 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.

Thanks, I like hearing "you don't have to do anything at all".

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

OK, so for ksummit-discuss and it's ilk I need

* ^List-Id: .*ksummit-discuss.lists.(linuxfoundation.org|linux.dev)

And I'll be good to go.

Thanks!

James



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Subscriber actions for migrating lists to lists.linux.dev
  2021-04-16 21:22   ` James Bottomley
@ 2021-04-16 21:26     ` Konstantin Ryabitsev
  0 siblings, 0 replies; 4+ messages in thread
From: Konstantin Ryabitsev @ 2021-04-16 21:26 UTC (permalink / raw)
  To: James Bottomley; +Cc: users, tools

On Fri, Apr 16, 2021 at 02:22:58PM -0700, James Bottomley wrote:
> >  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.
> 
> OK, so for ksummit-discuss and it's ilk I need
> 
> * ^List-Id: .*ksummit-discuss.lists.(linuxfoundation.org|linux.dev)

Note, that the new list is without the -discuss part, just
ksummit@lists.linux.dev, so you'll probably want:

* ^List-Id: .*ksummit.*\.lists\.linux.*

-K

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, back to index

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-16 20:58 Subscriber actions for migrating lists to lists.linux.dev James Bottomley
2021-04-16 21:16 ` Konstantin Ryabitsev
2021-04-16 21:22   ` James Bottomley
2021-04-16 21:26     ` Konstantin Ryabitsev

Linux maintainer tooling and workflows

Archives are clonable:
	git clone --mirror https://lore.kernel.org/tools/0 tools/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 tools tools/ https://lore.kernel.org/tools \
		tools@linux.kernel.org
	public-inbox-index tools

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.linux.tools


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git