linux-kernel - Re: [PATCH] MAINTAINERS: co-maintain random.c

lists.openwall.net		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] [thread-next>] [day] [month] [year] [list]

Message-ID: <YauCkjsgDL4sdCId@mit.edu>
Date:   Sat, 4 Dec 2021 10:00:34 -0500
From:   "Theodore Y. Ts'o" <tytso@....edu>
To:     "Jason A. Donenfeld" <Jason@...c4.com>
Cc:     Joe Perches <joe@...ches.com>, LKML <linux-kernel@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] MAINTAINERS: co-maintain random.c

On Wed, Dec 01, 2021 at 11:05:31AM -0500, Jason A. Donenfeld wrote:
> Hi Joe,
> 
> On Tue, Nov 30, 2021 at 8:01 PM Joe Perches <joe@...ches.com> wrote:
> > I suggest you reverse the entry order too as Ted really
> > hasn't done much to random.c for quite awhile.
> 
> Linus applied this already, but also, I both don't think the order
> really matters that much, and I'd really rather this be a "co-" thing,
> rather than rocking the boat.

Jason,

Thanks for stepping up.  There's no question that this Fall has been
insanely busy for me, and for the past 3 weeks or so, I've been on
vacation and Thanksgiving travel, and I'm still catching up on a
mountain of e-mail.

Something that I think would make sense is that we set up a joint git
tree on git.kernel.org, for which we would both have access to push
to, and use a group maintainership model much like what other teams
have done.  Do you agree?

						- Ted