lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Tue, 3 Jan 2023 22:18:16 -0800
From:   Eric Biggers <>
To:     Theodore Ts'o <>
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:
> > > 
> > > [...]
> > > L:
> > > Q:
> > > T:      git git://
> > > [...]
> This makes sense to me.  I wonder if we should use the new
> mailing list hosting service with a mailing
> list name
> 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 are archived on
>, 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, for
consistency with most of the existing lists...  But it does seem that the ship
on new lists using has already sailed.  So I think I'll go with

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