From: John Snow <jsnow@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add git-publish profile for security bugs
Date: Mon, 12 Aug 2019 13:58:05 -0400 [thread overview]
Message-ID: <20a99cc9-de01-8182-1c75-07dd07b5b35c@redhat.com> (raw)
In-Reply-To: <20190812071212.24551-1-kraxel@redhat.com>
On 8/12/19 3:12 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 | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/.gitpublish b/.gitpublish
> index a13f8c7c0ecd..55750c45ed89 100644
> --- a/.gitpublish
> +++ b/.gitpublish
> @@ -49,3 +49,14 @@ 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
>
Should we force inspect-emails = true here due to the nature of the
security list? That way if we accidentally add extra CCs/etc there's a
chance to review 'em.
Also, should we update MAINTAINERS to match this script?
Responsible Disclosure, Reporting Security Issues
-------------------------------------------------
W: https://wiki.qemu.org/SecurityProcess
M: Michael S. Tsirkin <mst@redhat.com>
L: secalert@redhat.com
With perhaps a footnote encouraging anyone changing this section to also
update the git-publish script and vice-versa?
--js
next prev parent reply other threads:[~2019-08-12 17:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 7:12 [Qemu-devel] [PATCH] Add git-publish profile for security bugs Gerd Hoffmann
2019-08-12 17:58 ` John Snow [this message]
2019-08-13 5:04 ` Gerd Hoffmann
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=20a99cc9-de01-8182-1c75-07dd07b5b35c@redhat.com \
--to=jsnow@redhat.com \
--cc=kraxel@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).