xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Jeff Kubascik <jeff.kubascik@dornerworks.com>
Cc: DornerWorks Xen-Devel <xen-devel@dornerworks.com>,
	Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	George Dunlap <george.dunlap@citrix.com>,
	Robert VanVossen <robert.vanvossen@dornerworks.com>,
	Tim Deegan <tim@xen.org>, Julien Grall <julien.grall@arm.com>,
	Josh Whitehead <josh.whitehead@dornerworks.com>,
	xen-devel@lists.xenproject.org,
	Jarvis Roach <Jarvis.Roach@dornerworks.com>
Subject: Re: [Xen-devel] [PATCH] MAINTAINERS: Add DornerWorks maintainers email
Date: Thu, 24 Oct 2019 15:37:56 +0200	[thread overview]
Message-ID: <924715ed-8eff-e611-ddfc-a9f5cb77e4c1@suse.com> (raw)
In-Reply-To: <dabf9641-4c16-767f-1623-7082f4be84ee@dornerworks.com>

On 24.10.2019 15:06, Jeff Kubascik wrote:
> We would like to remove our current two developers who are listed as M: for the
> ARINC653 scheduler code. Since M: is just a "Mail patches to" designation, I'm
> now leaning towards the L: designation, as the two appear roughly equivalent in
> their role. Does that sound reasonable?

While I realize what you say matches what the description of
M: says in ./MAINTAINERS, I'm afraid we also assign the
meaning of "is the maintainer of" to it, i.e. L: is not a
suitable equivalent (at least I don't think a list can
reasonably be considered a "maintainer"). It should perhaps
rather be R: the have this meaning.

As a side note, in addition I notice that M: says to mail
patches _to_ the listed people, which contradicts information
on e.g. the wiki where people are asked to send patches _to_
the list, with maintainers _cc_-ed (personally I prefer the
latter very much).

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      parent reply	other threads:[~2019-10-24 13:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-23 14:08 [Xen-devel] [PATCH] MAINTAINERS: Add DornerWorks maintainers email Jeff Kubascik
2019-08-23 14:11 ` George Dunlap
2019-08-23 14:21   ` Jeff Kubascik
2019-08-30  9:28 ` Wei Liu
2019-10-21 11:29   ` George Dunlap
2019-10-21 11:43     ` Wei Liu
2019-10-24 13:06       ` Jeff Kubascik
2019-10-24 13:36         ` Julien Grall
2019-10-24 16:19           ` Stewart Hildebrand
2019-10-24 13:37         ` Jan Beulich [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=924715ed-8eff-e611-ddfc-a9f5cb77e4c1@suse.com \
    --to=jbeulich@suse.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Jarvis.Roach@dornerworks.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jeff.kubascik@dornerworks.com \
    --cc=josh.whitehead@dornerworks.com \
    --cc=julien.grall@arm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=robert.vanvossen@dornerworks.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wl@xen.org \
    --cc=xen-devel@dornerworks.com \
    --cc=xen-devel@lists.xenproject.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).