xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Lars Kurth <lars.kurth@citrix.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Andrew Cooper <Andrew.Cooper3@citrix.com>,
	"Tim \(Xen.org\)" <tim@xen.org>,
	George Dunlap <George.Dunlap@citrix.com>,
	Jan Beulich <jbeulich@suse.com>,
	Ian Jackson <Ian.Jackson@citrix.com>
Subject: Re: [Xen-devel] [PATCH v4 2/3] Add V section entry to allow identification of Xen MAINTAINERS file
Date: Tue, 10 Sep 2019 17:01:16 +0100	[thread overview]
Message-ID: <5b343183-ed1f-6819-226c-a17acfd025a7@arm.com> (raw)
In-Reply-To: <E95BE9F8-9D7C-414B-BB33-1124CD55330F@citrix.com>

Hi Lars,

On 9/10/19 4:35 PM, Lars Kurth wrote:
> 
> On 10/09/2019, 16:31, "Julien Grall" <julien.grall@arm.com> wrote:
> 
>      Hi,
>      
>      Actually, I have one question about the template (my ack still stands).
>      
>      On 9/10/19 4:18 PM, Julien Grall wrote:
>      > Hi Lars,
>      >
>      > On 9/4/19 12:30 PM, Lars Kurth wrote:
>      >> This change provides sufficient information to allow get_maintainer.pl /
>      >> add_maintainers.pl scripts to be run on xen sister repositories such as
>      >> mini-os.git, osstest.git, etc
>      >>
>      >> A suggested template for sister repositories of Xen is
>      >>
>      >> ========================================================
>      >> This file follows the same conventions as outlined in
>      >> xen.git:MAINTAINERS. Please refer to the file in xen.git
>      >> for more information.
>      >>
>      >> THE REST
>      >> M:      MAINTAINER1 <maintainer1@email.com>
>      >> M:      MAINTAINER2 <maintainer2@email.com>
>      >> L:      xen-devel@lists.xenproject.org
>      
>      I was under the impression that the scripts would be used for Unikraft.
>      If so, do we expect them to CC xen-devel everytime?
> 
> In that case, the template has to be adapted. I was mainly thinking of
> XTF, OSSTEST, livepatch-build-tools. If it were used say for minios
> (which I think it should)  the L: field would obviously need changing
>   
> Once this series is through, I will submit maintainer files for all those
> projects making sure that they have the right L: field.
> 
>      If the answer is no, then we will probably want to add_maintainers.pl.
>      
> I basically dropped the original patch for Unikraft as nobody has responded.
> I was not planning to pick this up, unless someone from Unikraft runs with it

It makes sense. Thank you for the explanation!

Cheers,

-- 
Julien Grall

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

  reply	other threads:[~2019-09-10 16:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04 11:30 [Xen-devel] [PATCH v4 0/3] Allow get_maintainer.pl / add_maintainers.pl scripts to be called outside of xen.git Lars Kurth
2019-09-04 11:30 ` [Xen-devel] [PATCH v4 1/3] Remove hardcoding from scripts/add_maintainers.pl Lars Kurth
2019-09-10 15:17   ` Julien Grall
2019-09-04 11:30 ` [Xen-devel] [PATCH v4 2/3] Add V section entry to allow identification of Xen MAINTAINERS file Lars Kurth
2019-09-10 15:18   ` Julien Grall
2019-09-10 15:31     ` Julien Grall
2019-09-10 15:35       ` Lars Kurth
2019-09-10 16:01         ` Julien Grall [this message]
2019-09-04 11:30 ` [Xen-devel] [PATCH v4 3/3] Add logic to use V section entry in THE REST for identifying xen trees Lars Kurth
2019-09-11 15:41   ` Ian Jackson

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=5b343183-ed1f-6819-226c-a17acfd025a7@arm.com \
    --to=julien.grall@arm.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=Ian.Jackson@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=lars.kurth@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=tim@xen.org \
    --cc=wl@xen.org \
    --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).