qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Thomas Huth <thuth@redhat.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 14:47:26 +0200	[thread overview]
Message-ID: <212cc356-d1ce-3576-4616-01ec1eec1da2@redhat.com> (raw)
In-Reply-To: <20180827143731.26a5c0f6.cohuck@redhat.com>

>>
>>> * More trees to pull from. Of course, not every area needs a dedicated
>>>   tree (that would become silly pretty quickly), but for example a tcg
>>>   tree would be nice. I can still pick individual patches if a pull
>>>   request would be overkill.
>>> * 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.  
>>
>> Is the current setup with Richard (TCG) and myself (KVM) not good enough?
> 
> It's mostly "I'm uncomfortable that it's only me". Having the tcg
> maintainers resp. you handle things is absolutely fine for the usual
> run of things. The only time where there might be problems is if e.g.
> tcg and kvm changes interact in a non-trivial way, but I expect these
> to be very rare.

I wonder what kind of persons do things like that ;)

But yes, it should be rare and usually can wait in case you are on vacation.

-- 

Thanks,

David / dhildenb

      reply	other threads:[~2018-08-27 12:58 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
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 [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=212cc356-d1ce-3576-4616-01ec1eec1da2@redhat.com \
    --to=david@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=thuth@redhat.com \
    /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).