From: Kashyap Chamarthy <kchamart@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: pbonzini@redhat.com, eblake@redhat.com, qemu-devel@nongnu.org,
qemu-security@nongnu.org, peter.maydell@linaro.org
Subject: Re: [PATCH v2 1/3] docs: rSTify "security-process" page; move it to QEMU Git
Date: Tue, 15 Mar 2022 14:42:15 +0100 [thread overview]
Message-ID: <YjCXl7V+eapPJwc6@paraplu> (raw)
In-Reply-To: <89c85796-9853-e2fe-977b-2ab321c29af5@redhat.com>
On Tue, Mar 15, 2022 at 01:47:38PM +0100, Thomas Huth wrote:
> On 14/03/2022 11.49, Kashyap Chamarthy wrote:
[...]
> > + - Once the patch is merged, close the upstream bug with a link to
> > + the commit
> > +
> > + - Fixed in:
>
> There used to be a "<commit hash/link>" after that "Fixed in" on the
> original page, seems like you've lost that somewhere along the way?
Ouch, Pandoc seems to have eaten it during conversion, because of "< >"?
(But it didn't eat "<qemu-security@nongnu.org>" or
"<secalert@redhat.com>" at the top ... probably because they're
hyperlinks.) Anyway, I'll add it back in v2.
Thanks for the eagle eyes!
> Anyway, I'd like to hear from the security folks whether they are OK with
> moving this page to the main git repo, or whether it rather should stay in
> the qemu-web repo.
Sure.
--
/kashyap
next prev parent reply other threads:[~2022-03-15 13:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 10:49 [PATCH v2 0/3] rSTify a few more docs; move them to QEMU Git Kashyap Chamarthy
2022-03-14 10:49 ` [PATCH v2 1/3] docs: rSTify "security-process" page; move it " Kashyap Chamarthy
2022-03-15 12:47 ` Thomas Huth
2022-03-15 13:42 ` Kashyap Chamarthy [this message]
2022-03-14 10:49 ` [PATCH v2 2/3] docs: rSTify MailingLists wiki; " Kashyap Chamarthy
2022-03-14 13:45 ` Philippe Mathieu-Daudé
2022-03-14 15:10 ` Kashyap Chamarthy
2022-03-15 13:25 ` Thomas Huth
2022-03-15 16:00 ` Kashyap Chamarthy
2022-03-15 16:12 ` Peter Maydell
2022-03-21 9:55 ` Kashyap Chamarthy
2022-03-21 11:01 ` Peter Maydell
2022-03-21 11:18 ` Kashyap Chamarthy
2022-03-14 10:49 ` [PATCH v2 3/3] docs: rSTify GettingStartedDevelopers " Kashyap Chamarthy
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=YjCXl7V+eapPJwc6@paraplu \
--to=kchamart@redhat.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-security@nongnu.org \
--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).