From: "Leif Lindholm" <leif.lindholm@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: devel@edk2.groups.io, "Feng, Bob C" <bob.c.feng@intel.com>,
Liming Gao <liming.gao@intel.com>, Andrew Fish <afish@apple.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
"Wu, Hao A" <hao.a.wu@intel.com>
Subject: Re: [edk2-devel] [RFC PATCH 1/3] Maintainers.txt: update for filesystem area descriptions
Date: Thu, 20 Jun 2019 16:22:18 +0100 [thread overview]
Message-ID: <20190620152218.nfvdplyesev6nhuk@bivouac.eciton.net> (raw)
In-Reply-To: <45e43942-d64f-4155-fa41-3bc3d481f751@redhat.com>
On Thu, Jun 20, 2019 at 05:13:53PM +0200, Laszlo Ersek wrote:
> On 06/14/19 22:21, Leif Lindholm wrote:
> > Add comment describing new F: and X: tags for associating maintainership
> > sections with specific filesystem paths, including wildcards.
> >
> > Add global section associating *all* code with devel@edk2.groups.io,
> > and add a magic '<default>' F: tag directing all modifications that
> > do not hit a rule to the stewards.
> >
> > Also tag all files in top directory as maintained by the stewards.
> >
> > Signed-off-by: Leif Lindholm <leif.lindholm@linaro.org>
> > ---
> > Maintainers.txt | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 50 insertions(+)
> >
> > diff --git a/Maintainers.txt b/Maintainers.txt
> > index 762a68465979..cd32f9b00170 100644
> > --- a/Maintainers.txt
> > +++ b/Maintainers.txt
> > @@ -36,6 +36,20 @@ Descriptions of section entries:
> > Obsolete: Old code. Something tagged obsolete generally means
> > 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 per section acceptable.
>
> (1) Looks good, but I suggest updating the example pathnames so they
> feel more "native" to edk2 (use actual edk2 pathnames as examples?)
I could have sworn I changed those too...
Yeah, definitely will fix for v1.
> > + X: Files and directories that are NOT maintained, same rules as F:
> > + Files exclusions are tested after file matches.
> > + Can be useful for excluding a specific subdirectory, for instance:
> > + F: NetworkPkg/
> > + X: NetworkPkg/Ip6Dxe/
> > + matches all files in and below NetworkPkg excluding NetworkPkgnet/Ip6Dxe/
>
> Yep, this feels native.
>
> > + Magic filename "<default>" denotes all files not caught by any F: rule should
> > + be sent.
>
> (2) drop "should be sent"? (Sorry if my English parser failed me.)
Actually, this was meant to be
Magic filename "<default>" denotes where all files not caught by any F: rule
should be sent. ^ ^
But I like your version better.
> With those updates:
>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Thanks!
/
Leif
prev parent reply other threads:[~2019-06-20 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 20:21 [RFC PATCH 1/3] Maintainers.txt: update for filesystem area descriptions Leif Lindholm
2019-06-15 6:01 ` [edk2-devel] " Philippe Mathieu-Daudé
2019-06-18 3:30 ` Ni, Ray
[not found] ` <15A92D638F8524EE.27464@groups.io>
2019-06-18 5:32 ` Ni, Ray
2019-06-18 11:17 ` Leif Lindholm
2019-06-20 15:13 ` Laszlo Ersek
2019-06-20 15:22 ` Leif Lindholm [this message]
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-list 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=20190620152218.nfvdplyesev6nhuk@bivouac.eciton.net \
--to=devel@edk2.groups.io \
/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