all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Aaron Lauterer <a.lauterer@proxmox.com>
Subject: [pve-devel] partially-applied: [PATCH docs v2 1/5] pvecm: drop notes about old version incompatibilities
Date: Thu, 17 Jul 2025 01:04:36 +0200	[thread overview]
Message-ID: <175270707278.3543917.6178722618152511162.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250627134455.2065020-2-a.lauterer@proxmox.com>

On Fri, 27 Jun 2025 15:44:49 +0200, Aaron Lauterer wrote:
> 


Applied the docs patches, thanks!


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2025-07-16 23:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27 13:44 [pve-devel] [PATCH docs/manager v2 0/7] by expanding on it in the docs and the UI Aaron Lauterer
2025-06-27 13:44 ` [pve-devel] [PATCH docs v2 1/5] pvecm: drop notes about old version incompatibilities Aaron Lauterer
2025-07-16 23:04   ` Thomas Lamprecht [this message]
2025-06-27 13:44 ` [pve-devel] [PATCH docs v2 2/5] pvecm: add anchor for cluster requirements Aaron Lauterer
2025-06-27 13:44 ` [pve-devel] [PATCH docs v2 3/5] pvecm: add anchor for corosync exernal vote support Aaron Lauterer
2025-06-27 13:44 ` [pve-devel] [PATCH docs v2 4/5] pvecm: extend cluster Requirements Aaron Lauterer
2025-06-27 13:44 ` [pve-devel] [PATCH docs v2 5/5] ha-manager: expand requirements Aaron Lauterer
2025-06-27 13:44 ` [pve-devel] [PATCH manager v2 1/2] ui: cluster create: add recommendations for cluster networks Aaron Lauterer
2025-06-27 13:44 ` [pve-devel] [PATCH manager v2 2/2] ui: guest import: make sure an external link has target _blank Aaron Lauterer

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=175270707278.3543917.6178722618152511162.b4-ty@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=a.lauterer@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