From: John Snow <jsnow@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] Add git-publish profile for security bugs
Date: Tue, 13 Aug 2019 14:45:35 -0400 [thread overview]
Message-ID: <ab03f068-ca21-dc99-68d4-d53a98f3d3b7@redhat.com> (raw)
In-Reply-To: <20190813090727.18058-1-kraxel@redhat.com>
On 8/13/19 5:07 AM, Gerd Hoffmann wrote:
> Simplifies sending security patches to all people listed in
> https://wiki.qemu.org/SecurityProcess. Should also make it
> harder to send a copy to the mailing list by accident.
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> .gitpublish | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/.gitpublish b/.gitpublish
> index a13f8c7c0ecd..01f8279fa840 100644
> --- a/.gitpublish
> +++ b/.gitpublish
> @@ -49,3 +49,15 @@ base = master
> to = qemu-devel@nongnu.org
> cc = qemu-ppc@nongnu.org
> cccmd = scripts/get_maintainer.pl --noroles --norolestats --nogit --nogit-fallback 2>/dev/null
> +
> +# https://wiki.qemu.org/SecurityProcess
> +[gitpublishprofile "security"]
> +base = master
> +to = mst@redhat.com
> +to = pmatouse@redhat.com
> +to = sstabellini@kernel.org
> +to = secalert@redhat.com
> +to = mdroth@linux.vnet.ibm.com
> +to = pjp@redhat.com
> +suppresscc = all
> +inspect-emails = true
>
OK, but it still would be nice to have the MAINTAINERS file and this
config item cross-reference each other, especially because any changes
to our security policy should not leave hanging loose ends.
next prev parent reply other threads:[~2019-08-13 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 9:07 [Qemu-devel] [PATCH v2] Add git-publish profile for security bugs Gerd Hoffmann
2019-08-13 18:45 ` John Snow [this message]
2019-08-15 14:00 ` Stefan Hajnoczi
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=ab03f068-ca21-dc99-68d4-d53a98f3d3b7@redhat.com \
--to=jsnow@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.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).