qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [PATCH] docs/devel: fix stable process doc formatting
Date: Tue, 21 Jan 2020 18:06:13 +0100	[thread overview]
Message-ID: <20200121180613.13551328.cohuck@redhat.com> (raw)
In-Reply-To: <20200113103023.31255-1-cohuck@redhat.com>

On Mon, 13 Jan 2020 11:30:23 +0100
Cornelia Huck <cohuck@redhat.com> wrote:

> Enumeration of stable criteria needs proper bullet points.
> 
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
>  docs/devel/stable-process.rst | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/docs/devel/stable-process.rst b/docs/devel/stable-process.rst
> index 98736a9ea487..e541b983fac7 100644
> --- a/docs/devel/stable-process.rst
> +++ b/docs/devel/stable-process.rst
> @@ -18,8 +18,10 @@ What should go into a stable release?
>  -------------------------------------
>  
>  Generally, the following patches are considered stable material:
> -- Patches that fix severe issues, like fixes for CVEs
> -- Patches that fix regressions
> +
> +* Patches that fix severe issues, like fixes for CVEs
> +
> +* Patches that fix regressions
>  
>  If you think the patch would be important for users of the current release
>  (or for a distribution picking fixes), it is usually a good candidate

Queued to s390-next, so that it doesn't fall through the cracks.



      parent reply	other threads:[~2020-01-21 17:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 10:30 [PATCH] docs/devel: fix stable process doc formatting Cornelia Huck
2020-01-14 11:04 ` Stefan Hajnoczi
2020-01-21 17:06 ` 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=20200121180613.13551328.cohuck@redhat.com \
    --to=cohuck@redhat.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).