[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <38bf64245d173d0de4452cac1c6cf028ad0490d8.camel@perches.com>
Date: Fri, 06 Sep 2019 09:20:35 -0700
From: Joe Perches <joe@...ches.com>
To: Mauro Carvalho Chehab <mchehab+samsung@...nel.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Linux Media Mailing List <linux-media@...r.kernel.org>,
Mauro Carvalho Chehab <mchehab@...radead.org>,
linux-kernel@...r.kernel.org, Jonathan Corbet <corbet@....net>,
Jessica Yu <jeyu@...nel.org>,
Federico Vaga <federico.vaga@...a.pv.it>,
Thomas Gleixner <tglx@...utronix.de>, linux-doc@...r.kernel.org
Subject: Re: [PATCH] docs: license-rules.txt: cover SPDX headers on Python
scripts
On Fri, 2019-09-06 at 11:45 -0300, Mauro Carvalho Chehab wrote:
> Em Fri, 06 Sep 2019 05:20:30 -0700
> Joe Perches <joe@...ches.com> escreveu:
>
> > On Fri, 2019-09-06 at 08:34 -0300, Mauro Carvalho Chehab wrote:
> > > I did some changes on it, plus one change at the pedantic mode of
> > > scripts/spdxcheck.py, and placed the corresponding patches at:
> > >
> > > https://git.linuxtv.org/mchehab/experimental.git/log/?h=spdx_pedantic
> >
> > Overall seems very nice, thanks.
> >
> > Couple nits.
> >
> > Some of the scripts and py files move the author
> > block into a description or add unnecessary blank
> > comments. These may use some manual fixups.
>
> True. I noticed that too. I suspect that fixing this automatically would
> make the script too complex.
>
> Anyway, the point is: who will apply it? Linus? Each maintainer?
I have been advocating for a treewide scripted mechanism for awhile.
https://lore.kernel.org/lkml/4398924f28a58fca296d101dae11e7accce80656.camel@perches.com/
Powered by blists - more mailing lists