From: Kashyap Chamarthy <kchamart@redhat.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, thuth@redhat.com, peter.maydell@linaro.org,
eblake@redhat.com
Subject: [PATCH v3 0/4] rSTify a few more docs; move them to QEMU Git
Date: Mon, 6 Jun 2022 18:55:47 +0200 [thread overview]
Message-ID: <Yp4xk2+JeNkZ5eTv@pinwheel> (raw)
In-Reply-To: <Yp4wKGhyMtAj/Jx2@pinwheel>
On Mon, Jun 06, 2022 at 06:49:49PM +0200, Kashyap Chamarthy wrote:
> Oops, messed up v3's cover-letter subject; now fixed. Sorry.
Sigh, instead of "v3", I accidentally wrote "v4" in the cover-letter
subject. Now fix that too; sorry for the noise.
> On Mon, Jun 06, 2022 at 06:43:32PM +0200, Kashyap Chamarthy wrote:
> > - Add back the "<commit hash/link>" fragment in security-process.rst
> > [Thomas]
> > - Add a docs/about/contacting-the-project.rst as per Peter's feedback
> > here:
> > https://lists.nongnu.org/archive/html/qemu-devel/2022-03/msg05178.html
> > [pm215]
> > - Keep Thomas' R-by for "docs: rSTify MailingLists wiki; move it to QEMU
> > Git"
> >
> > v2 cover letter:
> > -----------------------------------------------------------------------
> > rSTify a few more docs; move them to QEMU Git
> >
> > This series rST-ifies:
> >
> > - security-process[1]
> > - MailingLists[2]
> > - GettingStartedDevelopers[3]
> >
> > The 'security-process' page is from the QEMU web and is moved to
> > docs/devel/ in QEMU Git. This is based on Paolo's feedback here[4].
> > The next two docs are converted from the Wiki.
> >
> > [1] https://www.qemu.org/contribute/security-process
> > [2] https://wiki.qemu.org/Contribute/MailingLists
> > [3] https://wiki.qemu.org/Documentation/GettingStartedDevelopers
> > [4] https://lists.nongnu.org/archive/html/qemu-devel/2021-11/msg04002.html
> > -----------------------------------------------------------------------
> >
> > Kashyap Chamarthy (4):
> > docs: rSTify "security-process" page; move it to QEMU Git
> > docs: rSTify MailingLists wiki; move it to QEMU Git
> > docs: rSTify GettingStartedDevelopers wiki; move it to QEMU Git
> > Add a new doc "contacting-the-project.rst"
> >
> > docs/about/contacting-the-project.rst | 16 ++
> > docs/about/index.rst | 1 +
> > docs/devel/getting-started-developers.rst | 200 ++++++++++++++++++++++
> > docs/devel/index.rst | 3 +
> > docs/devel/mailing-lists.rst | 51 ++++++
> > docs/devel/security-process.rst | 190 ++++++++++++++++++++
> > 6 files changed, 461 insertions(+)
> > create mode 100644 docs/about/contacting-the-project.rst
> > create mode 100644 docs/devel/getting-started-developers.rst
> > create mode 100644 docs/devel/mailing-lists.rst
> > create mode 100644 docs/devel/security-process.rst
> >
> > --
> > 2.36.1
> >
>
> --
> /kashyap
--
/kashyap
next prev parent reply other threads:[~2022-06-06 16:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 16:43 [PATCH v3 0/4] In v3: Kashyap Chamarthy
2022-06-06 16:43 ` [PATCH v3 1/4] docs: rSTify "security-process" page; move it to QEMU Git Kashyap Chamarthy
2022-06-06 16:43 ` [PATCH v3 2/4] docs: rSTify MailingLists wiki; " Kashyap Chamarthy
2022-06-06 21:53 ` Alistair Francis
2022-06-08 5:46 ` Thomas Huth
2022-06-10 10:23 ` Kashyap Chamarthy
2022-06-06 16:43 ` [PATCH v3 3/4] docs: rSTify GettingStartedDevelopers " Kashyap Chamarthy
2022-07-01 10:06 ` Peter Maydell
2022-06-06 16:43 ` [PATCH v3 4/4] Add a new doc "contacting-the-project.rst" Kashyap Chamarthy
2022-06-08 5:50 ` Thomas Huth
2022-06-06 16:49 ` [PATCH v4 0/4] rSTify a few more docs; move them to QEMU Git [Was: Re: [PATCH v3 0/4] In v3:] Kashyap Chamarthy
2022-06-06 16:55 ` Kashyap Chamarthy [this message]
2022-07-01 8:53 ` [PATCH v3 0/4] rSTify a few more docs; move them to QEMU Git Kashyap Chamarthy
2022-07-01 10:07 ` Peter Maydell
2022-07-04 15:12 ` Thomas Huth
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=Yp4xk2+JeNkZ5eTv@pinwheel \
--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).