From: Joe Perches <joe@perches.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Michal Marek <mmarek@suse.cz>,
Cesar Eduardo Barros <cesarb@cesarb.net>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
David Howells <dhowells@redhat.com>
Subject: Re: [PATCH] scripts: add checkmaintainers.py
Date: Mon, 17 Dec 2012 07:35:44 -0800 [thread overview]
Message-ID: <1355758544.13361.14.camel@joe-AO722> (raw)
In-Reply-To: <20121217102714.GB31947@liondog.tnic>
On Mon, 2012-12-17 at 11:27 +0100, Borislav Petkov wrote:
> On Mon, Dec 17, 2012 at 11:14:24AM +0100, Michal Marek wrote:
> > On 14.12.2012 23:19, Cesar Eduardo Barros wrote:
> > > This small script checks the file patterns in the MAINTAINERS file.
> > >
> > > For every file pattern, it checks if the pattern matches any file or
> > > directory in the kernel tree, printing the patterns which do not have a
> > > match.
> >
> > Can't this be added as a warning to scripts/get_maintainer.pl instead?
>
> Yep, it definitely makes more sense than having a standalone script.
I'm not so sure of that myself.
I think maybe it should go into checkpatch.
I do have a similar script as a get_maintainers variant.
Adding a --verify-patterns option seems off-topic to
the generic tool use of get_maintainers.
There's a fair amount of tedium for people to do more
than determine there is a pattern that doesn't match
files in git.
Doing the work that Cesar did to find the commit that
makes a pattern valid/invalid when renames or deletions
occur is the chore that could be automated.
Perhaps Cesar can use his script as a starting point
to find those pattern invalidating commits or maybe
add the capability (or a --strict check) to checkpatch.
next prev parent reply other threads:[~2012-12-17 15:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 22:19 Cesar Eduardo Barros
2012-12-17 10:14 ` Michal Marek
2012-12-17 10:27 ` Borislav Petkov
2012-12-17 15:35 ` Joe Perches [this message]
2012-12-17 17:00 ` Borislav Petkov
2012-12-17 18:56 ` Joe Perches
2012-12-17 19:09 ` Joe Perches
2012-12-18 18:28 ` Borislav Petkov
2012-12-18 19:34 ` Joe Perches
2012-12-18 20:31 ` Borislav Petkov
2012-12-18 20:36 ` Joe Perches
2012-12-18 20:47 ` Borislav Petkov
2012-12-18 21:33 ` Joe Perches
2012-12-19 15:07 ` Borislav Petkov
2012-12-19 17:43 ` Joe Perches
2012-12-20 19:31 ` Borislav Petkov
2012-12-17 21:59 ` Cesar Eduardo Barros
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1355758544.13361.14.camel@joe-AO722 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=cesarb@cesarb.net \
--cc=dhowells@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®