From: Cornelia Huck <cohuck@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org, qemu-s390x <qemu-s390x@nongnu.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: s390: Remove myself
Date: Tue, 30 Oct 2018 17:56:44 +0100 [thread overview]
Message-ID: <20181030175644.232e9163.cohuck@redhat.com> (raw)
In-Reply-To: <20181030093715.18793-1-agraf@suse.de>
On Tue, 30 Oct 2018 10:37:15 +0100
Alexander Graf <agraf@suse.de> wrote:
> I haven't realistically maintained s390 related parts for quite a while
> now, so let's remove my name from the MATINAINERS file to reflect reality.
>
> Signed-off-by: Alexander Graf <agraf@suse.de>
> ---
> MAINTAINERS | 4 ----
> 1 file changed, 4 deletions(-)
Thank you again for your past work!
Queued (with the typo fixed) to s390-next.
prev parent reply other threads:[~2018-10-30 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 9:37 [Qemu-devel] [PATCH] MAINTAINERS: s390: Remove myself Alexander Graf
2018-10-30 14:34 ` Philippe Mathieu-Daudé
2018-10-30 16:56 ` Cornelia Huck [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=20181030175644.232e9163.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
/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).