From: "Theodore Ts'o" <tytso@mit.edu>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-fscrypt@vger.kernel.org, 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: Separate mailing list (and git and patchwork) for fsverity?
Date: Thu, 22 Dec 2022 11:51:23 -0500 [thread overview]
Message-ID: <Y6SLC9DG1s/4NhPL@mit.edu> (raw)
In-Reply-To: <Y6ObULdVm2UN5kw1@sol.localdomain>
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@vger.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@lsts.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
WARNING: multiple messages have this Message-ID (diff)
From: "Theodore Ts'o" <tytso@mit.edu>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, linux-fscrypt@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-btrfs@vger.kernel.org
Subject: Re: [f2fs-dev] Separate mailing list (and git and patchwork) for fsverity?
Date: Thu, 22 Dec 2022 11:51:23 -0500 [thread overview]
Message-ID: <Y6SLC9DG1s/4NhPL@mit.edu> (raw)
In-Reply-To: <Y6ObULdVm2UN5kw1@sol.localdomain>
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@vger.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@lsts.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
_______________________________________________
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-22 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 19:24 Separate mailing list (and git and patchwork) for fsverity? Eric Biggers
2022-12-13 19:24 ` [f2fs-dev] " Eric Biggers
2022-12-21 23:48 ` Eric Biggers
2022-12-21 23:48 ` [f2fs-dev] " Eric Biggers
2022-12-22 16:51 ` Theodore Ts'o [this message]
2022-12-22 16:51 ` Theodore Ts'o
2023-01-04 6:18 ` Eric Biggers
2023-01-04 6:18 ` [f2fs-dev] " 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=Y6SLC9DG1s/4NhPL@mit.edu \
--to=tytso@mit.edu \
--cc=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 \
/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.