From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P . Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>
Subject: [PULL 5/5] qemu-doc: Clarify extent of build platform support
Date: Sat, 15 Feb 2020 14:05:27 +0100 [thread overview]
Message-ID: <20200215130527.28861-6-armbru@redhat.com> (raw)
In-Reply-To: <20200215130527.28861-1-armbru@redhat.com>
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>
Message-Id: <20200213084335.15100-1-armbru@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
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
next prev parent reply other threads:[~2020-02-15 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 13:05 [PULL 0/5] Monitor patches for 2020-02-15 Markus Armbruster
2020-02-15 13:05 ` [PULL 1/5] monitor: Move monitor option parsing to monitor/monitor.c Markus Armbruster
2020-02-15 13:05 ` [PULL 2/5] qapi: Split control.json off misc.json Markus Armbruster
2020-02-15 13:05 ` [PULL 3/5] monitor: Collect "control" command handlers in qmp-cmds.control.c Markus Armbruster
2020-02-15 13:05 ` [PULL 4/5] monitor: Move qmp_query_qmp_schema to qmp-cmds-control.c Markus Armbruster
2020-02-15 13:05 ` Markus Armbruster [this message]
2020-02-17 10:00 ` [PULL 0/5] Monitor patches for 2020-02-15 Peter Maydell
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=20200215130527.28861-6-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@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).