From: Joe Perches <joe@perches.com>
To: Valdis.Kletnieks@vt.edu
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH] [2/2many] - FInd the maintainer(s) for a patch - MAINTAINERS
Date: Mon, 13 Aug 2007 09:45:43 -0700 [thread overview]
Message-ID: <1187023543.10249.107.camel@localhost> (raw)
In-Reply-To: <9866.1187022990@turing-police.cc.vt.edu>
On Mon, 2007-08-13 at 12:36 -0400, Valdis.Kletnieks@vt.edu wrote:
> On Sun, 12 Aug 2007 23:10:16 PDT, Joe Perches said:
>
> > + A trailing slash includes all files and subdirectory files.
> > + F: drivers/net/ all files in and below drivers/net
> > + F: drivers/net/* all files in drivers/net, but not below
>
> Since somebody is going to screw up and do it - what are the semantics
> of 'drivers/net' and forgetting the trailing slash?
Looks for a specific file in the patch called drivers/net
> is it silent or noisy (if it's silent, it won't get fixed)
silent
> + F: */net/* all files in "any top level directory"/net
> Does the leading '*' match exactly one level
Yes
> or will it match foo/bar/net/* as
No match, the script counts slashes
+sub file_match_pattern {
+ my ($file, $pattern) = @_;
+ if (substr($pattern, -1) eq "/") {
+ if ($file =~ m@^$pattern@) {
+ return 1;
+ }
+ } else {
+ if ($file =~ m@^$pattern@) {
+ my $s1 = ($file =~ tr@/@@);
+ my $s2 = ($pattern =~ tr@/@@);
+ if ($s1 == $s2) {
+ return 1;
+ }
+ }
+ }
+ return 0;
+}
Enhancements appreciated.
> Is a construction like 'net/*/netfilter/*' legal?
Yes
cheers, Joe
next prev parent reply other threads:[~2007-08-13 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 6:10 [PATCH] [2/2many] - FInd the maintainer(s) for a patch - MAINTAINERS Joe Perches
2007-08-13 16:36 ` Valdis.Kletnieks
2007-08-13 16:45 ` Joe Perches [this message]
2007-08-13 20:02 ` Richard Knutsson
2007-08-13 20:12 ` Joe Perches
-- strict thread matches above, loose matches on Subject: below --
2007-08-13 5:53 Joe Perches
2007-08-13 6:33 ` Muli Ben-Yehuda
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=1187023543.10249.107.camel@localhost \
--to=joe@perches.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.