[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5c2a49b12bb82279e51045eabf67055944cad3f2.camel@perches.com>
Date: Sun, 10 Feb 2019 18:21:28 -0800
From: Joe Perches <joe@...ches.com>
To: James Bottomley <jejb@...ux.ibm.com>,
Lukas Bulwahn <lukas.bulwahn@...il.com>,
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
Mimi Zohar <zohar@...uxibm.com>
Cc: linux-integrity@...r.kernel.org, keyrings@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: use tab instead of spaces
On Sun, 2019-02-10 at 10:25 -0800, James Bottomley wrote:
> On Sun, 2019-02-10 at 19:10 +0100, Lukas Bulwahn wrote:
> > Mimi Zohar used spaces instead of a tab when adding Jarkko Sakkinen
> > as
> > further maintainer to the KEYS-TRUSTED section entry. So, we rectify
> > this
> > with this commit.
> >
> > The issue was detected when writing a script that parses MAINTAINERS.
> >
> > Fixes: 34bccd61b139 ("MAINTAINERS: add Jarkko as maintainer for
> > trusted keys")
> > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@...il.com>
>
> This isn't really a bug, is it?
No, it's a style defect.
> We have no formatting requirements for the MAINTAINERS file and the
> section owner is free to align with tabs, spaces or nothing as they see
> fit. Most use a single tab, but a couple don't. The only real thing
> that cares is get_maintainers.pl and it uses \s* as the parse regexp,
> so it doesn't care either.
Not really.
It doesn't 'care' because get_maintainer is designed
to work with badly formatted entries.
checkpatch does emit warnings for MAINTAINER entries
that use anything other than a single tab.
Powered by blists - more mailing lists