qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: otubo@redhat.com
Cc: qemu-devel@nongnu.org
Subject: Re: Stepping down from seccomp mintainership
Date: Mon, 31 Jan 2022 14:31:26 +0000	[thread overview]
Message-ID: <YffyvhfUBDfa25eE@redhat.com> (raw)
In-Reply-To: <CAGMDDkd07FTemjXL=5OwTdx0ZEJv85wAp=AS--B_Po7qmu8=yg@mail.gmail.com>

On Mon, Jan 31, 2022 at 01:54:02PM +0100, Eduardo Otubo wrote:
> Hello all,
> 
> It's been a while since my last commit or pull request, and given the
> current state of things I don't think I'll be coming back to actual
> QEMU development. At least not as frequently as I wanted to have
> seccomp under my eyes at all times.
> 
> This being said, I'd like to retire as the seccomp maintainer. Anyone
> who wishes to take over from here is welcome to do so.

I've been responsible for a number of the seccomp patches, and the
overall change in design approach from deny-all-with-exceptions to
allow-all-with-exceptions. I don't especially want to take on more
work, but this feature doesn't see frequent changes, so I'd be ok
to pick this up in an 'odd fixes' role, unless some other maintainer
has a burning desire to invest more time.

I can send a MAINTAINERS file update swapping our names, in a few days
unless some else jumps in to volunteer in the meantime....

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



      reply	other threads:[~2022-01-31 14:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 12:54 Stepping down from seccomp mintainership Eduardo Otubo
2022-01-31 14:31 ` Daniel P. Berrangé [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=YffyvhfUBDfa25eE@redhat.com \
    --to=berrange@redhat.com \
    --cc=otubo@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).