From: Valdis.Kletnieks@vt.edu
To: Joe Perches <joe@perches.com>
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 12:36:30 -0400 [thread overview]
Message-ID: <9866.1187022990@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sun, 12 Aug 2007 23:10:16 PDT." <1186985416.10249.13.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
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? Does your tool break on
that, and if so, is it silent or noisy (if it's silent, it won't get fixed).
> + F: */net/* all files in "any top level directory"/net
Does the leading '*' match exactly one level, or will it match foo/bar/net/*
as well?
Is a construction like 'net/*/netfilter/*' legal?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-08-13 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 6:10 Joe Perches
2007-08-13 16:36 ` Valdis.Kletnieks [this message]
2007-08-13 16:45 ` Joe Perches
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=9866.1187022990@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--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 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®