From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, Friedrich Weber <f.weber@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs] pvecm: redundancy: explicitly mention subnets
Date: Tue, 9 Sep 2025 17:38:45 +0200 [thread overview]
Message-ID: <175743230661.177723.7334341652969069187.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250908145305.112814-1-f.weber@proxmox.com>
On Mon, 08 Sep 2025 16:52:24 +0200, Friedrich Weber wrote:
> The section uses addresses 10.10.10.X and 10.20.20.X in examples and
> implicitly assumes they are in disjoint subnets, but does not
> explicitly state this.
>
> For better clarity, explicitly mention these are /25 subnets (this
> subnet mask is also used in the "Separate Cluster Network" section).
>
> [...]
Applied, thanks!
[1/1] pvecm: redundancy: explicitly mention subnets
commit: feb34c347cd55ff31c99f39d077058f087e5dc5c
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-09-09 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 14:52 [pve-devel] " Friedrich Weber
2025-09-09 13:12 ` Maximiliano Sandoval
2025-09-09 15:38 ` Fiona Ebner [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=175743230661.177723.7334341652969069187.b4-ty@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=f.weber@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox