From: Alexander Zeidler <a.zeidler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] faq: change to inline anchors to land on the actual questions
Date: Mon, 23 Oct 2023 17:31:45 +0200 [thread overview]
Message-ID: <20231023153145.176237-1-a.zeidler@proxmox.com> (raw)
Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
---
pve-faq.adoc | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/pve-faq.adoc b/pve-faq.adoc
index 93fef32..2388673 100644
--- a/pve-faq.adoc
+++ b/pve-faq.adoc
@@ -77,8 +77,7 @@ CPU.
It is not limited to Linux guests but allows arbitrary operating systems
to run.
-[[faq-support-table]]
-How long will my {pve} version be supported?::
+[[faq-support-table]] How long will my {pve} version be supported?::
{pve} versions are supported at least as long as the corresponding
Debian Version is
@@ -99,8 +98,7 @@ recommended.
| {pve} 1 | Debian 5 (Lenny) | 2008-10 | 2012-03 | 2013-01
|===============================================================================
-[[faq-upgrade]]
-How can I upgrade {pve} to the next point release?::
+[[faq-upgrade]] How can I upgrade {pve} to the next point release?::
Minor version upgrades, for example upgrading from {pve} in version 7.1
to 7.2 or 7.3, can be done just like any normal update.
@@ -119,8 +117,7 @@ NOTE: Always ensure you correctly setup the
xref:sysadmin_package_repositories[package repositories] and only
continue with the actual upgrade if `apt update` did not hit any error.
-[[faq-upgrade-major]]
-How can I upgrade {pve} to the next major release?::
+[[faq-upgrade-major]] How can I upgrade {pve} to the next major release?::
Major version upgrades, for example going from {pve} 4.4 to 5.0, are also
supported.
--
2.39.2
next reply other threads:[~2023-10-23 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 15:31 Alexander Zeidler [this message]
2023-10-23 15:39 ` Thomas Lamprecht
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=20231023153145.176237-1-a.zeidler@proxmox.com \
--to=a.zeidler@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal