[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <32692.1568623971@warthog.procyon.org.uk>
Date: Mon, 16 Sep 2019 09:52:51 +0100
From: David Howells <dhowells@...hat.com>
To: Joe Perches <joe@...ches.com>
Cc: dhowells@...hat.com,
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
linux-integrity@...r.kernel.org, keyrings@...r.kernel.org,
Mimi Zohar <zohar@...ux.ibm.com>,
James Bottomley <jejb@...ux.ibm.com>,
Mauro Carvalho Chehab <mchehab+samsung@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Add a git and a maintainer entry to keyring subsystems
Joe Perches <joe@...ches.com> wrote:
> > I would recommend splitting the patch in two and putting something like:
> >
> > keys: Add Jarkko Sakkinen as co-maintainer
> >
> > as the subject of the keyrings maintainership one.
>
> Why is there utility in micro splitting such a trivial patch?
Because the keyrings maintainership piece is addressing a major procedural
concern on Linus's part - and I think it needs to go in its own patch with the
subject I suggested.
David
Powered by blists - more mailing lists