xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Stewart Hildebrand <stewart.hildebrand@dornerworks.com>,
	Henry Wang <Henry.Wang@arm.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	George Dunlap <george.dunlap@citrix.com>,
	Julien Grall <julien@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
	Jeff Kubascik <jeff.kubascik@dornerworks.com>,
	Nathan Studer <nathan.studer@dornerworks.com>,
	Robbie VanVossen <robert.vanvossen@dornerworks.com>,
	xen-devel@dornerworks.com, Stewart Hildebrand <stewart@stew.dk>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH] MAINTAINERS: change my email
Date: Fri, 16 Sep 2022 08:08:51 +0200	[thread overview]
Message-ID: <a83ac46b-3db8-7770-6f24-041de84a3392@suse.com> (raw)
In-Reply-To: <20220915193027.3166-1-stewart.hildebrand@dornerworks.com>

On 15.09.2022 21:30, Stewart Hildebrand wrote:
> I am departing DornerWorks. I will still be working with Xen in my next
> role, and I still have an interest in maintaining the ARINC 653
> scheduler, so change to my personal email address. Also change status to
> Maintained.
> 
> Signed-off-by: Stewart Hildebrand <stewart.hildebrand@dornerworks.com>
> ---
>  MAINTAINERS | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e12c499a28..f674b5f7ba 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -221,8 +221,8 @@ F:	xen/include/xen/argo.h
>  F:	xen/common/argo.c
>  
>  ARINC653 SCHEDULER
> -M:	Stewart Hildebrand <stewart.hildebrand@dornerworks.com>
> -S:	Supported
> +M:	Stewart Hildebrand <stewart@stew.dk>
> +S:	Maintained
>  L:	xen-devel@dornerworks.com
>  F:	xen/common/sched/arinc653.c
>  F:	tools/libs/ctrl/xc_arinc653.c

If it was just for the email change, I would have said it can go in without
release manager approval. But the support level change I think wants a
release ack at this point. Just to not leave the question unasked: There's
no interest within DornerWorks to have someone else be (co)maintainer of
this code?

Acked-by: Jan Beulich <jbeulich@suse.com>

Jan


  reply	other threads:[~2022-09-16  6:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15 19:30 [PATCH] MAINTAINERS: change my email Stewart Hildebrand
2022-09-16  6:08 ` Jan Beulich [this message]
2022-09-16  6:25   ` Henry Wang
2022-09-18 19:18   ` Stewart Hildebrand
2022-09-19  2:10 ` [PATCH v2] MAINTAINERS: ARINC 653 scheduler maintainer updates Stewart Hildebrand
2022-09-19  8:44   ` Jan Beulich
2022-09-26  8:56   ` Jan Beulich
2022-09-26 13:12     ` Nathan Studer

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=a83ac46b-3db8-7770-6f24-041de84a3392@suse.com \
    --to=jbeulich@suse.com \
    --cc=Henry.Wang@arm.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=jeff.kubascik@dornerworks.com \
    --cc=julien@xen.org \
    --cc=nathan.studer@dornerworks.com \
    --cc=robert.vanvossen@dornerworks.com \
    --cc=sstabellini@kernel.org \
    --cc=stewart.hildebrand@dornerworks.com \
    --cc=stewart@stew.dk \
    --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).