From: Thomas Huth <thuth@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>, David Hildenbrand <david@redhat.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Alexander Graf <agraf@suse.de>,
Richard Henderson <rth@twiddle.net>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFD] [s390x] Tweaking the s390x maintainership setup
Date: Mon, 27 Aug 2018 12:52:02 +0200 [thread overview]
Message-ID: <e6463614-cf70-6f2e-5d90-5ace62ce8aee@redhat.com> (raw)
In-Reply-To: <20180827124058.36aa13ee.cohuck@redhat.com>
On 2018-08-27 12:40, Cornelia Huck wrote:
> On Mon, 27 Aug 2018 11:26:21 +0200
> David Hildenbrand <david@redhat.com> wrote:
>
>> On 24.08.2018 13:37, Cornelia Huck wrote:
[...]
>>> * I'd also like to have a designated backup for the overall
>>> maintainership, especially for when I'm on vacation (like the first
>>> two weeks of September, just to let you know :) or otherwise
>>> unavailable, but also for sanity. Likely needs to be a non-IBMer due
>>> to the tcg problem.
>>
>> Either Thomas or I could do that. I will be on vacation the first two
>> weeks of September, too ;) Thomas, interested?
>
> Maybe both of you? I doubt we'll be on vacation during the same time
> period every time ;)
Hmm, we already have Christian for the non-TCG stuff, and Richard is
listed in MAINTAINERs in the S390 TCG section. So I think we should
already be fine to cover you during your holidays for all areas,
shouldn't we?
Anyway, sure, I can also keep my eyes on the incoming patches during the
two weeks.
Thomas
next prev parent reply other threads:[~2018-08-27 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 11:37 [Qemu-devel] [RFD] [s390x] Tweaking the s390x maintainership setup Cornelia Huck
2018-08-27 9:26 ` David Hildenbrand
2018-08-27 10:40 ` Cornelia Huck
2018-08-27 10:52 ` Thomas Huth [this message]
2018-08-27 11:33 ` Peter Maydell
2018-08-27 12:02 ` Christian Borntraeger
2018-08-27 12:37 ` Cornelia Huck
2018-08-27 12:47 ` David Hildenbrand
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=e6463614-cf70-6f2e-5d90-5ace62ce8aee@redhat.com \
--to=thuth@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--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).