From: Richard Knutsson <ricknu-0@student.ltu.se>
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 22:02:50 +0200 [thread overview]
Message-ID: <46C0B8EA.9080405@student.ltu.se> (raw)
In-Reply-To: <1186985416.10249.13.camel@localhost>
Joe Perches wrote:
> It helps when you do the diff the right way.
>
> Describe the new F: pattern
>
> Signed-off-by: Joe Perches <joe@perches.com>
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d3a0684..0d7f856 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -83,6 +83,13 @@ S: Status, one of the following:
> it has been replaced by a better system and you
> should be using that.
>
> +F: Files and directories with wildcard patterns.
> + 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
> + F: */net/* all files in "any top level directory"/net
> + One pattern per line. Multiple F: lines acceptable.
> +
> 3C359 NETWORK DRIVER
> P: Mike Phillips
> M: mikep@linuxtr.net
>
>
Just to be clear, which one is picked with a patch for drivers/net/foo?
Both or the most common one?
SUBSYSTEM1
P: Person 1
F: */net/
SUBSYSTEM2
P: Person 2
F: drivers/net/
Richard "the Perl-illiterate" Knutsson
next prev parent reply other threads:[~2007-08-13 20:04 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
2007-08-13 20:02 ` Richard Knutsson [this message]
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=46C0B8EA.9080405@student.ltu.se \
--to=ricknu-0@student.ltu.se \
--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 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.