From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: Christoph Heiss <c.heiss@proxmox.com>
Cc: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] applied-series: [PATCH pmg-docs 0/2] improve faq upgrade section
Date: Thu, 30 Jan 2025 14:01:13 +0100 [thread overview]
Message-ID: <Z5t4GSLo-3xUGO6H@rosa.proxmox.com> (raw)
In-Reply-To: <20241022112426.709562-1-c.heiss@proxmox.com>
applied both patches - thanks!
On Tue, Oct 22, 2024 at 01:24:23PM +0200, Christoph Heiss wrote:
> First, splits up the upgrade section into two, one for point release
> upgrades and one for major release upgrades. This makes the difference
> stand out better, and we have the same in pve-docs too.
>
> Secondly, fixes #5771 by adding the missing link for the 7->8 upgrade
> instructions in the wiki.
>
> Christoph Heiss (2):
> faq: split up upgrade section into major and point release upgrades
> fix #5771: faq: add 7 to 8 upgrade link
>
> pmg-faq.adoc | 19 +++++++++++++++----
> 1 file changed, 15 insertions(+), 4 deletions(-)
>
> --
> 2.46.0
>
>
>
> _______________________________________________
> pmg-devel mailing list
> pmg-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
>
>
_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
prev parent reply other threads:[~2025-01-30 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 11:24 [pmg-devel] " Christoph Heiss
2024-10-22 11:24 ` [pmg-devel] [PATCH pmg-docs 1/2] faq: split up upgrade section into major and point release upgrades Christoph Heiss
2024-10-22 11:24 ` [pmg-devel] [PATCH pmg-docs 2/2] fix #5771: faq: add 7 to 8 upgrade link Christoph Heiss
2025-01-30 13:01 ` Stoiko Ivanov [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=Z5t4GSLo-3xUGO6H@rosa.proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=c.heiss@proxmox.com \
--cc=pmg-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.