All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: jsnow@redhat.com, pbonzini@redhat.com, berrange@redhat.com,
	qemu-devel@nongnu.org, peter.maydell@linaro.org
Subject: Re: [PATCH] qemu-doc: Clarify extent of build platform support
Date: Thu, 13 Feb 2020 15:47:49 -0500	[thread overview]
Message-ID: <20200213204749.GC3455@habkost.net> (raw)
In-Reply-To: <20200213084335.15100-1-armbru@redhat.com>

On Thu, Feb 13, 2020 at 09:43:34AM +0100, Markus Armbruster wrote:
> Supporting a build platform beyond its end of life makes no sense.
> Spell that out just to be clear.
> 
> Signed-off-by: Markus Armbruster <armbru@redhat.com>

Thanks!

Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>

> ---
>  qemu-doc.texi | 9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/qemu-doc.texi b/qemu-doc.texi
> index a1ef6b6484..33b9597b1d 100644
> --- a/qemu-doc.texi
> +++ b/qemu-doc.texi
> @@ -2880,10 +2880,11 @@ lifetime distros will be assumed to ship similar software versions.
>  
>  For distributions with long-lifetime releases, the project will aim to support
>  the most recent major version at all times. Support for the previous major
> -version will be dropped 2 years after the new major version is released. For
> -the purposes of identifying supported software versions, the project will look
> -at RHEL, Debian, Ubuntu LTS, and SLES distros. Other long-lifetime distros will
> -be assumed to ship similar software versions.
> +version will be dropped 2 years after the new major version is released,
> +or when it reaches ``end of life''. For the purposes of identifying
> +supported software versions, the project will look at RHEL, Debian,
> +Ubuntu LTS, and SLES distros. Other long-lifetime distros will be
> +assumed to ship similar software versions.
>  
>  @section Windows
>  
> -- 
> 2.21.1
> 

-- 
Eduardo



      parent reply	other threads:[~2020-02-13 20:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-13  8:43 [PATCH] qemu-doc: Clarify extent of build platform support Markus Armbruster
2020-02-13  9:30 ` Daniel P. Berrangé
2020-02-13 20:47 ` Eduardo Habkost [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=20200213204749.GC3455@habkost.net \
    --to=ehabkost@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.