From: Kevin Wolf <kwolf@redhat.com>
To: jdillama@redhat.com
Cc: jdurgin@redhat.com, Jason Dillaman <dillaman@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: update RBD block maintainer
Date: Fri, 28 Jun 2019 16:59:21 +0200 [thread overview]
Message-ID: <20190628145921.GO5179@dhcp-200-226.str.redhat.com> (raw)
In-Reply-To: <20190628135508.8013-1-dillaman@redhat.com>
Am 28.06.2019 um 15:55 hat jdillama@redhat.com geschrieben:
> From: Jason Dillaman <dillaman@redhat.com>
>
> Remove Josh as per his request since he is no longer the upstream RBD
> tech lead. Add myself as the maintainer since I am the current RBD tech
> lead.
>
> Signed-off-by: Jason Dillaman <dillaman@redhat.com>
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2019-06-28 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 13:55 [Qemu-devel] [PATCH] MAINTAINERS: update RBD block maintainer jdillama
2019-06-28 14:35 ` Josh Durgin
2019-06-28 14:59 ` Kevin Wolf [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=20190628145921.GO5179@dhcp-200-226.str.redhat.com \
--to=kwolf@redhat.com \
--cc=dillaman@redhat.com \
--cc=jdillama@redhat.com \
--cc=jdurgin@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).