From: Cornelia Huck <cohuck@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] docs: document our stable process
Date: Fri, 16 Feb 2018 11:34:24 +0100 [thread overview]
Message-ID: <20180216113424.54e980d0.cohuck@redhat.com> (raw)
In-Reply-To: <CAFEAcA_JpeUeWoxyhTzzPAkH-Kc0OwV-r91LP=Mt27z1=icdQA@mail.gmail.com>
On Thu, 15 Feb 2018 18:27:29 +0000
Peter Maydell <peter.maydell@linaro.org> wrote:
> On 12 February 2018 at 12:40, Cornelia Huck <cohuck@redhat.com> wrote:
> > Some pointers on how to get a patch into stable.
> >
> > [contains some suggestions by mdroth]
> > Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> > ---
> > RFC/D->v2: added mdroth's suggestions
> > ---
> > docs/stable-process.rst | 67 +++++++++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 67 insertions(+)
> > create mode 100644 docs/stable-process.rst
> >
>
> Drive-by bikeshed comment: should this be in docs/devel ?
> It's aimed at QEMU developers rather than users...
I don't mind moving the shed over to docs/devel/.
OK, I have merged the various comments and pushed the result to
git://github.com/cohuck/qemu stable-doc
Who will merge this? I can send a pull request if needed.
prev parent reply other threads:[~2018-02-16 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 12:40 [Qemu-devel] [PATCH v2] docs: document our stable process Cornelia Huck
2018-02-12 17:17 ` Eric Blake
2018-02-12 17:58 ` Cornelia Huck
2018-02-15 18:08 ` Michael Roth
2018-02-15 18:27 ` Peter Maydell
2018-02-16 10:34 ` Cornelia Huck [this message]
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=20180216113424.54e980d0.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=eblake@redhat.com \
--cc=mdroth@linux.vnet.ibm.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).