From: Lars Kurth <lars.kurth@citrix.com>
To: George Dunlap <George.Dunlap@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Wei Liu <wei.liu2@citrix.com>, "Keir (Xen.org)" <keir@xen.org>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
"Tim (Xen.org)" <tim@xen.org>, Jan Beulich <jbeulich@suse.com>,
Ian Jackson <Ian.Jackson@citrix.com>
Subject: Re: [PATCH] MAINTAINERS: Clarify the meaning of nested maintainership
Date: Tue, 26 Apr 2016 16:57:28 +0000 [thread overview]
Message-ID: <D3455BB4.28A6D%lars.kurth@citrix.com> (raw)
In-Reply-To: <571F9522.7040408@citrix.com>
On 26/04/2016 17:19, "George Dunlap" <george.dunlap@citrix.com> wrote:
>On 21/04/16 17:59, Lars Kurth wrote:
>>
>>
>> On 21/04/2016 17:03, "George Dunlap" <george.dunlap@citrix.com> wrote:
>>
>>> Clarify the meaning of nested maintainership.
>>>
>>> Signed-off-by: George Dunlap <george.dunlap@citrix.com>
>>> ---
>>>
>>> MAINTAINERS | 34 ++++++++++++++++++++++++++++++++++
>>> 1 file changed, 34 insertions(+)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index a34685d..be901d5 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -94,6 +94,40 @@ Descriptions of section entries:
>>> printk, pr_info or pr_err
>>> One regex pattern per line. Multiple K: lines acceptable.
>>>
>>> +
>>> +The meaning of nesting:
>>> +
>>>
>>> [snip]
>>
>>> + - In the case of a disagreement between maintainers, THE REST can
>>> + vote to settle the matter. (This should be very exceptional indeed.)
>>
>> This creates a slight conflict with the project governance, which states
>> that committers act as referees in case of disagreements. As REST
>> maintainers are a superset of committers, this could create a potential
>> mismatch.
>>
>> Given, that the text says "can", I don't have an issue with it. It
>>merely
>> adds an extra level of complexity when it comes to resolving
>>disagreements
>> and maybe could be confusing.
>
>With Keir gone, is that actually the case anymore? I think at the
>moment REST == committers.
>
>And the logic behind putting the committers under the REST seemed to me
>in part to make the logic match up.
That is fine with me. I just picked up on it, because further up the patch
you said
+Many maintanership areas are "nested": for example, there are entries
+for xen/arch/x86 as well as xen/arch/x86/mm, and even
+xen/arch/x86/mm/shadow; and there is a section at the end called "THE
+REST" which lists all committers, as well as a few more.
^^^^^^^^^^^^^^^^^^^^^
Lars
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-26 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 16:03 [PATCH] MAINTAINERS: Clarify the meaning of nested maintainership George Dunlap
2016-04-21 16:59 ` Lars Kurth
2016-04-26 16:19 ` George Dunlap
2016-04-26 16:57 ` Lars Kurth [this message]
2016-04-27 11:34 ` George Dunlap
2016-04-22 3:55 ` Juergen Gross
2016-04-22 8:29 ` Jan Beulich
2016-04-22 16:33 ` Andrew Cooper
2016-04-22 18:33 ` Julien Grall
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=D3455BB4.28A6D%lars.kurth@citrix.com \
--to=lars.kurth@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).