From: Jarkko Sakkinen Date: Mon, 16 Sep 2019 18:23:32 +0000 Subject: Re: [PATCH] MAINTAINERS: Add a git and a maintainer entry to keyring subsystems Message-Id: <20190916182332.GC16093@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit List-Id: References: <33da71451cbc5836efd61ccf125be89c6e946253.camel@perches.com> <20190910143228.30305-1-jarkko.sakkinen@linux.intel.com> <11580.1568387033@warthog.procyon.org.uk> <32692.1568623971@warthog.procyon.org.uk> In-Reply-To: <32692.1568623971@warthog.procyon.org.uk> To: David Howells Cc: Joe Perches , linux-integrity@vger.kernel.org, keyrings@vger.kernel.org, Mimi Zohar , James Bottomley , Mauro Carvalho Chehab , "David S. Miller" , Greg Kroah-Hartman , Nicolas Ferre , open list On Mon, Sep 16, 2019 at 09:52:51AM +0100, David Howells wrote: > Joe Perches 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. I'll send separate patches tomorrow. /Jarkko