[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190914125444.GC9560@linux.intel.com>
Date: Sat, 14 Sep 2019 13:54:44 +0100
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Joe Perches <joe@...ches.com>
Cc: David Howells <dhowells@...hat.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
On Fri, Sep 13, 2019 at 10:36:15AM -0700, Joe Perches wrote:
> 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?
I kind of get this for the MAINTAINERS file so that the changes can
be agreed/disagreed separately.
/Jarkko
Powered by blists - more mailing lists