All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Tim Deegan <tim@xen.org>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir@xen.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Julien Grall <julien.grall@citrix.com>,
	David Vrabel <david.vrabel@citrix.com>,
	Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v2] MAINTAINERS: Document maintainers for xen/common/
Date: Thu, 17 Sep 2015 19:02:44 +0100	[thread overview]
Message-ID: <22011.68.956821.565239@mariner.uk.xensource.com> (raw)
In-Reply-To: <20150917122316.GA43280@deinos.phlegethon.org>

Tim Deegan writes ("Re: [PATCH v2] MAINTAINERS: Document maintainers for xen/common/"):
> I would rather your v1 plus an appropriate change to get_maintainers.

I am happy to implement in get_maintainers whatever is decided.

At the moment there is one kind of fallback:

(i) `THE REST' gets CCd iff no file pointed to any other maintainer

What you may be proposing is a subtly different kind of fallback:

(ii) `REST OF THE HYPERVISOR' gets CCd iff the patch touches any files
   in xen/ which do not have another maintainer

The difference is apparent in patches which touch both more specific
and less specific items.

Alternatively maybe you are proposing that we should have two
hierarchical fallbacks: `REST OF THE HYPERVISOR' gets CCd if any file
is in xen/ is touched but is skipped BUT only if no file pointed to
another maintainer.

Ian.

  reply	other threads:[~2015-09-17 18:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 11:53 [PATCH v2] MAINTAINERS: Document maintainers for xen/common/ Ian Jackson
2015-09-17 11:59 ` Andrew Cooper
2015-09-17 12:04   ` Julien Grall
2015-09-17 12:23 ` Tim Deegan
2015-09-17 18:02   ` Ian Jackson [this message]
2015-09-18  6:02     ` Jan Beulich
2015-09-18 10:13     ` Tim Deegan

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=22011.68.956821.565239@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien.grall@citrix.com \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xensource.com \
    /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.