xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wl@xen.org>
To: George Dunlap <george.dunlap@citrix.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>,
	Jeff Kubascik <jeff.kubascik@dornerworks.com>,
	Tim Deegan <tim@xen.org>, Julien Grall <julien.grall@arm.com>,
	Josh Whitehead <josh.whitehead@dornerworks.com>,
	Robert VanVossen <robert.vanvossen@dornerworks.com>,
	Jan Beulich <jbeulich@suse.com>,
	xen-devel@lists.xenproject.org,
	Jarvis Roach <Jarvis.Roach@dornerworks.com>
Subject: Re: [Xen-devel] [PATCH] MAINTAINERS: Add DornerWorks maintainers email
Date: Mon, 21 Oct 2019 12:43:48 +0100	[thread overview]
Message-ID: <20191021114348.kynwzrkbl4xbnfky@debian> (raw)
In-Reply-To: <5bf66876-8b09-bb34-bc4f-046d6e1e4205@citrix.com>

On Mon, Oct 21, 2019 at 12:29:45PM +0100, George Dunlap wrote:
> On 8/30/19 10:28 AM, Wei Liu wrote:
> > On Fri, Aug 23, 2019 at 10:08:55AM -0400, Jeff Kubascik wrote:
> >> We would like to have a common maintainers email address for DornerWorks
> >> maintained code, which currently is the ARINC653 scheduler. This will
> >> enable us to better monitor and respond to the Xen community. This patch
> >> adds a maintainer line with the DornerWorks maintainers email address.
> >> ---
> >>  MAINTAINERS | 1 +
> >>  1 file changed, 1 insertion(+)
> >>
> >> diff --git a/MAINTAINERS b/MAINTAINERS
> >> index 77413e0d9e..3cce253931 100644
> >> --- a/MAINTAINERS
> >> +++ b/MAINTAINERS
> >> @@ -168,6 +168,7 @@ F:	xen/common/argo.c
> >>  ARINC653 SCHEDULER
> >>  M:	Josh Whitehead <josh.whitehead@dornerworks.com>
> >>  M:	Robert VanVossen <robert.vanvossen@dornerworks.com>
> >> +M:	DornerWorks Xen-Devel <xen-devel@dornerworks.com>
> > 
> > The correct symbol here is L. 
> > 
> >     L: Mailing list that is relevant to this area
> 
> But this isn't exactly a mailing list, is it?  The 'L:' tag is normally
> for things like the Linux Arm mailing list, the Linux Net mailing list,
> and so on -- *public* lists where discussions about that subsystem happen.
> 
> This isn't a public list where discussion happens.  At the moment, in
> fact, it looks like it might be a *single email account*, to which
> several people have access; at best it would be an alias that would go
> to a number of interested parties.  That seems closer to 'R:'.
> 
> I admit this is getting into the minutia of technicalities here. :-)
> 

My understanding is that the list being public is a not a requirement.
For example, Linux has this:

  L:      sparmaintainer@unisys.com (Unisys internal)

An alias for several people still qualifies as a list to me.

Anyway, either R or L works. I don't want to bikeshed further...

Wei.

>  -George

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

  reply	other threads:[~2019-10-21 11:44 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 [this message]
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

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=20191021114348.kynwzrkbl4xbnfky@debian \
    --to=wl@xen.org \
    --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=jbeulich@suse.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=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).