qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Moore <pmoore@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Eduardo Otubo <otubo@linux.vnet.ibm.com>,
	Anthony Liguori <anthony@codemonkey.ws>
Cc: coreyb@linux.vnet.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] seccomp submaintainer? (was Re: [PATCH] seccomp: adding times() to the whitelist)
Date: Mon, 09 Sep 2013 10:44:40 -0400	[thread overview]
Message-ID: <5541403.3IaE33qAHr@sifl> (raw)
In-Reply-To: <522DD199.2020508@redhat.com>

On Monday, September 09, 2013 03:48:09 PM Paolo Bonzini wrote:
> Il 09/09/2013 15:20, Eduardo Otubo ha scritto:
> >> Out of respect for the work that Eduardo has done, and is
> >> continuing to do, with the QEMU seccomp filtering, I think Eduardo
> >> should be the one to take on this role. If Eduardo declines I'll do
> >> ahead and submit a patch adding myself to the MAINTAINERS file.
> > 
> > If this is ok for everyone, I would be really glad to take this role to
> > myself. Paul, thanks for this vote of confidence. Paolo, should I send a
> > patch for MAINTAINERS right away?
> 
> Ok, I was suggesting Paul because he was the one doing reviews.
> 
> Eduardo, that is also okay for me.  However, even as a maintainer please
> do wait for Paul's reviews.  Many areas of QEMU have maintainers that do
> not send their own patches without a review, so this wouldn't be a new
> rule. :)

Okay, with respect to maintainership, I was thinking more along the lines of 
the Linux Kernel where those that do the work get the job; it looks like QEMU 
has a slightly different twist on the idea.  If it makes more sense to the 
QEMU devs you can always add me as a co-maintainer.

Regardless, I do plan on continuing to review/test patches and I don't expect 
that to change in the near future.

> Please wait for Anthony's ack.  I changed the subject and CCed him to
> grab his attention.
> 
> Paolo

-- 
paul moore
security and virtualization @ redhat

  reply	other threads:[~2013-09-09 14:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 12:25 [Qemu-devel] [PATCH] seccomp: adding times() to the whitelist Eduardo Otubo
2013-09-04 13:10 ` Corey Bryant
2013-09-04 14:11 ` Paul Moore
2013-09-06 18:41   ` Eduardo Otubo
2013-09-09 10:38     ` Paolo Bonzini
2013-09-09 12:36       ` Paul Moore
2013-09-09 13:20         ` Eduardo Otubo
2013-09-09 13:48           ` [Qemu-devel] seccomp submaintainer? (was Re: [PATCH] seccomp: adding times() to the whitelist) Paolo Bonzini
2013-09-09 14:44             ` Paul Moore [this message]
2013-09-09 16:40             ` Anthony Liguori
2013-09-13 14:45   ` [Qemu-devel] [PATCH] seccomp: adding times() to the whitelist Paul Moore
2013-09-23 19:49     ` Eduardo Otubo
2013-09-23 19:54       ` Anthony Liguori
2013-09-23 19:53   ` Paul Moore
2013-09-23 19:56     ` Eduardo Otubo

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=5541403.3IaE33qAHr@sifl \
    --to=pmoore@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=coreyb@linux.vnet.ibm.com \
    --cc=otubo@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --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).