[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <33da71451cbc5836efd61ccf125be89c6e946253.camel@perches.com>
Date: Fri, 13 Sep 2019 10:36:15 -0700
From: Joe Perches <joe@...ches.com>
To: David Howells <dhowells@...hat.com>,
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
Cc: 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
On Fri, 2019-09-13 at 16:03 +0100, David Howells wrote:
> Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com> wrote:
>
> > Subject: [PATCH] MAINTAINERS: Add a git and a maintainer entry to keyring subsystems
>
> 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?
Powered by blists - more mailing lists