From: Joe Perches <joe@perches.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Matthew Wilcox <willy@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: rectify radix-tree testing entry in XARRAY
Date: Sat, 01 Feb 2020 15:35:23 -0800 [thread overview]
Message-ID: <5ac73de311101754a25aaeac3df1aca23dbaf2af.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2002012231410.5859@felia>
On Sat, 2020-02-01 at 22:35 +0100, Lukas Bulwahn wrote:
>
> On Sat, 1 Feb 2020, Lukas Bulwahn wrote:
>
> > The initial commit 3d5bd6e1a04a ("xarray: Add MAINTAINERS entry")
> > missed a trailing slash to include all files and subdirectory files.
> > Hence, all files in tools/testing/radix-tree were not part of XARRAY,
> > but were considered to be part of "THE REST".
> >
> > Rectify this to ensure patches reach the actual maintainer.
> >
> > This was identified with a small script that finds all files only
> > belonging to "THE REST" according to the current MAINTAINERS file, and I
> > acted upon its output.
> >
> > Fixes: 3d5bd6e1a04a ("xarray: Add MAINTAINERS entry")
> > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> > ---
> > Matthew, please pick this small fixup patch.
> >
> > applies cleanly on current master and next-20200131
> >
>
> Matthew, Joe Perches just informed me that get_maintainers.pl is smart
> enough to handle the case below and does not strictly need a further
> trailing slash.
>
> Please ignore this patch; the commit message is actually wrong.
While the commit message may be inexact,
I think the actual change is good and
could/should still be applied.
The "Fixes:" tag is unnecessary though.
prev parent reply other threads:[~2020-02-01 23:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 18:02 Lukas Bulwahn
2020-02-01 21:35 ` Lukas Bulwahn
2020-02-01 23:35 ` Joe Perches [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-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=5ac73de311101754a25aaeac3df1aca23dbaf2af.camel@perches.com \
--to=joe@perches.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=willy@infradead.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®