qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC/D] docs: document our stable process
Date: Mon, 12 Feb 2018 13:36:24 +0100	[thread overview]
Message-ID: <20180212133624.34dd2f49.cohuck@redhat.com> (raw)
In-Reply-To: <151840458286.28114.4120688586561065910@sif>

On Sun, 11 Feb 2018 21:03:02 -0600
Michael Roth <mdroth@linux.vnet.ibm.com> wrote:

> Quoting Cornelia Huck (2018-02-09 07:11:12)
> > Some pointers on how to get a patch into stable.  
> 
> Thanks for putting this together. I made some minor suggestions below
> that might help clarify some points.
> 
> > 
> > Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> > ---
> > 
> > This probably needs more love, but I'd like to have at least _some_
> > kind of documentation.
> > 
> > Maybe this should also go into the wiki?  
> 
> We can probably add a reference to it in:
> 
>   https://wiki.qemu.org/Contribute/SubmitAPatch

Yes, it makes sense to add a pointer once this is upstream.

> 
> I should probably add a MAINTAINERS entry for stable that references
> it too.

+1

> 
> > 
> > ---
> >  docs/stable-process.rst | 57 +++++++++++++++++++++++++++++++++++++++++++++++++
> >  1 file changed, 57 insertions(+)
> >  create mode 100644 docs/stable-process.rst

<snip>

I have incorporated your suggestions (sometimes massaged a bit). v2 on
the way.

Thanks for your feedback!

      reply	other threads:[~2018-02-12 12:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09 13:11 [Qemu-devel] [PATCH RFC/D] docs: document our stable process Cornelia Huck
2018-02-12  3:03 ` Michael Roth
2018-02-12 12:36   ` 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=20180212133624.34dd2f49.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=mdroth@linux.vnet.ibm.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).