From: Kashyap Chamarthy <kchamart@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, thuth@redhat.com,
Kashyap Chamarthy <kchamart@redhat.com>,
eblake@redhat.com, pbonzini@redhat.com
Subject: [PATCH 0/2] rSTify 'report-a-bug' and 'security-process'; move them to QEMU Git
Date: Wed, 24 Nov 2021 15:27:26 +0100 [thread overview]
Message-ID: <20211124142728.1221817-1-kchamart@redhat.com> (raw)
This series rSTifies the said web pages[1][2] from the QEMU web and
moves them to docs/devel/ in QEMU Git. This is based on Paolo's
feedback here[3].
The rename to 'reporting-a-bug' is done to be consistent with the other
in-tree docs. And I put 'security-process' first because, we refer to
it from 'reporting-a-bug'. (If we reverse the order, the build fails --
correctly so.)
[1] https://www.qemu.org/contribute/report-a-bug/
[2] https://www.qemu.org/contribute/security-process
[3] https://lists.nongnu.org/archive/html/qemu-devel/2021-11/msg04002.html
Kashyap Chamarthy (2):
docs: rSTify "security-process" page; move it to QEMU Git
docs: rSTify "report-a-bug" page; move it to QEMU Git
docs/devel/index.rst | 9 +-
docs/devel/reporting-a-bug.rst | 37 +++++++
docs/devel/security-process.rst | 190 ++++++++++++++++++++++++++++++++
3 files changed, 233 insertions(+), 3 deletions(-)
create mode 100644 docs/devel/reporting-a-bug.rst
create mode 100644 docs/devel/security-process.rst
--
2.31.1
next reply other threads:[~2021-11-24 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 14:27 Kashyap Chamarthy [this message]
2021-11-24 14:27 ` [PATCH 1/2] docs: rSTify "security-process" page; move it to QEMU Git Kashyap Chamarthy
2021-11-29 13:33 ` Peter Maydell
2021-11-24 14:27 ` [PATCH 2/2] docs: rSTify "report-a-bug" " Kashyap Chamarthy
2021-11-29 13:35 ` Peter Maydell
2021-12-03 9:27 ` 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=20211124142728.1221817-1-kchamart@redhat.com \
--to=kchamart@redhat.com \
--cc=eblake@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@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).