From: Thomas Huth <thuth@redhat.com>
To: Palmer Dabbelt <palmer@sifive.com>, philmd@redhat.com
Cc: qemu-riscv@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-3.1 1/2] MAINTAINERS: Any file with "riscv" in the name is a RISC-V file
Date: Thu, 22 Nov 2018 10:09:16 +0100 [thread overview]
Message-ID: <1a6f23a1-fba1-578b-38cb-4274177ee7d5@redhat.com> (raw)
In-Reply-To: <mhng-ce1dc513-eb34-4ace-b3a2-248347025887@palmer-si-x1c4>
On 2018-11-22 02:44, Palmer Dabbelt wrote:
> On Wed, 21 Nov 2018 16:29:09 PST (-0800), philmd@redhat.com wrote:
>> On 22/11/18 0:46, Palmer Dabbelt wrote:
>>> There was a recent thread about unmaintained files in QEMU where it was
>>> noted that a few RISC-V related files had slipped through the patterns
>>> in our MAINTAINERS file entry. This patch adds some more aggressive
>>> pattern matching in an attempt to rectify this situation.
>>>
>>> Signed-off-by: Palmer Dabbelt <palmer@sifive.com>
>>> ---
>>> MAINTAINERS | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 1032406c5607..e89adc81d5d5 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -255,6 +255,8 @@ F: target/riscv/
>>> F: hw/riscv/
>>> F: include/hw/riscv/
>>> F: disas/riscv.c
>>> +K: riscv
Please be very careful with the "K:" lines ... you could suddenly end up
being a "maintainer" for files that you did not expect. For example,
after applying your patch, I guess the following commands will tell you
that you're the maintainer of these files:
script/get_maintainer.pl -f MAINTAINERS
script/get_maintainer.pl -f qapi/misc.json
script/get_maintainer.pl -f configure
...
For this reason, we've limited the "K:" lines in MAINTAINERS so far to
files that contain the regex "^Subject:", too (so that they only match
patches with the keyword in the subject).
>>> +N: riscv
>>
>> QEMU doesn't support the 'N' tag.
>> I see from the Linux kernel:
>>
>> N: Files and directories with regex patterns.
>> N: [^a-z]tegra all files whose path contains the word tegra
>> One pattern per line. Multiple N: lines acceptable.
>> scripts/get_maintainer.pl has different behavior for files that
>> match F: pattern and matches of N: patterns. By default,
>> get_maintainer will not look at git log history when an F: pattern
>> match occurs. When an N: match occurs, git log history is used
>> to also notify the people that have git commit signatures.
>>
>> Should we add this feature to checkscript?
>
> Ah, I didn't check because I just copied this from our Linux entry.
> It's pretty much the core of what I'm trying to do here so if it's easy
> then that'd be great.
>
> Unfortunately I don't know how to do so.
Try to export the commits eb90d0855 and bbbe96ed8 from the Linux kernel
git and see whether the patches can be applied to our version of
get_maintainers.pl, too.
HTH,
Thomas
prev parent reply other threads:[~2018-11-22 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 23:46 [Qemu-devel] [PATCH for-3.1 1/2] MAINTAINERS: Any file with "riscv" in the name is a RISC-V file Palmer Dabbelt
2018-11-21 23:46 ` [Qemu-devel] [PATCH for-3.1 2/2] MAINTAINERS: Mark RISC-V as Supported Palmer Dabbelt
2018-11-22 2:10 ` Alistair Francis
2018-11-22 0:29 ` [Qemu-devel] [PATCH for-3.1 1/2] MAINTAINERS: Any file with "riscv" in the name is a RISC-V file Philippe Mathieu-Daudé
2018-11-22 1:44 ` Palmer Dabbelt
2018-11-22 9:09 ` Thomas Huth [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=1a6f23a1-fba1-578b-38cb-4274177ee7d5@redhat.com \
--to=thuth@redhat.com \
--cc=palmer@sifive.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.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;
as well as URLs for NNTP newsgroup(s).