From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org, "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] Separate mailing list (and git and patchwork) for fsverity?
Date: Wed, 21 Dec 2022 15:48:32 -0800 [thread overview]
Message-ID: <Y6ObULdVm2UN5kw1@sol.localdomain> (raw)
In-Reply-To: <Y5jRbLEJh3S46Jer@sol.localdomain>
On Tue, Dec 13, 2022 at 11:24:28AM -0800, Eric Biggers wrote:
> Currently, fsverity development is reusing the same mailing list, git repo
> (though a different branch), and patchwork project as fscrypt --- mainly just
> because I was a little lazy and didn't bother to ask for new ones:
>
> FSCRYPT: FILE SYSTEM LEVEL ENCRYPTION SUPPORT
> [...]
> L: linux-fscrypt@vger.kernel.org
> Q: https://patchwork.kernel.org/project/linux-fscrypt/list/
> T: git git://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git
> [...]
>
> FSVERITY: READ-ONLY FILE-BASED AUTHENTICITY PROTECTION
> [...]
> L: linux-fscrypt@vger.kernel.org
> Q: https://patchwork.kernel.org/project/linux-fscrypt/list/
> T: git git://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git fsverity
> [...]
>
> I think this is causing some confusion. It also makes it so that people can't
> subscribe to the list for just one or the other.
>
> 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@vger.kernel.org
> Q: https://patchwork.kernel.org/project/linux-fsverity/list/
> T: git git://git.kernel.org/pub/scm/fs/fsverity/fsverity.git
> [...]
>
> For the branches in the git repo, I'm thinking of using 'for-next' and
> 'for-current'. (I'd also update the fscrypt ones to match; currently they are
> 'master' and 'for-stable'.)
>
> If people are okay with these changes, I'll send off the needed requests to
> helpdesk and linux-next to make these changes, and send Linus a pull request to
> update MAINTAINERS. (And update fsverity-utils to point to the new list.)
>
Any thoughts on this from anyone?
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-12-21 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 19:24 [f2fs-dev] Separate mailing list (and git and patchwork) for fsverity? Eric Biggers
2022-12-21 23:48 ` Eric Biggers [this message]
2022-12-22 16:51 ` Theodore Ts'o
2023-01-04 6:18 ` Eric Biggers
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=Y6ObULdVm2UN5kw1@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
/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).