[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y7UaKGqKPHsZyZn8@sol.localdomain>
Date: Tue, 3 Jan 2023 22:18:16 -0800
From: Eric Biggers <ebiggers@...nel.org>
To: Theodore Ts'o <tytso@....edu>
Cc: linux-fscrypt@...r.kernel.org, linux-xfs@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-btrfs@...r.kernel.org, linux-f2fs-devel@...ts.sourceforge.net
Subject: Re: Separate mailing list (and git and patchwork) for fsverity?
On Thu, Dec 22, 2022 at 11:51:23AM -0500, Theodore Ts'o wrote:
> On Wed, Dec 21, 2022 at 03:48:32PM -0800, Eric Biggers wrote:
> > > What would people say about having a separate mailing list, git repo, and
> > > patchwork project for fsverity? So the fsverity entry would look like:
> > >
> > > FSVERITY: READ-ONLY FILE-BASED AUTHENTICITY PROTECTION
> > > [...]
> > > L: linux-fsverity@...r.kernel.org
> > > Q: https://patchwork.kernel.org/project/linux-fsverity/list/
> > > T: git git://git.kernel.org/pub/scm/fs/fsverity/fsverity.git
> > > [...]
>
> This makes sense to me. I wonder if we should use the new
> https://lists.linux.dev mailing list hosting service with a mailing
> list name fsverity@...s.linux.dev?
>
> The thinking was that we would eventually migrate lists from vger to
> the new list infrastructure, so it might make sense to just use it for
> a new list. All mailing lists lists.linux.dev are archived on
> lore.kernel.org, so other than the e-mail address and using something
> a bit more modern than Majordomo for list management, it's mostly the
> same.
>
> - Ted
Thanks Ted! I'm half-tempted to still use linux-fsverity@...r.kernel.org, for
consistency with most of the existing lists... But it does seem that the ship
on new lists using lists.linux.dev has already sailed. So I think I'll go with
fsverity@...ts.linux.dev.
Any other opinions from anyone on this, or on the proposed new git repo and
branches, before I send off the helpdesk request?
- Eric
Powered by blists - more mailing lists