From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [PATCH docs] cluster join: mention that storage config from cluster is inherited
Date: Mon, 16 Jan 2023 16:55:17 +0100 [thread overview]
Message-ID: <03f87272-dc10-2fe6-a176-22dfff324142@proxmox.com> (raw)
In-Reply-To: <20221130140934.130359-1-f.ebner@proxmox.com>
Am 30/11/2022 um 15:09 schrieb Fiona Ebner:
> and what to do about it. It's a rather common topic in forum threads.
>
> Suggested in the community forum:
> https://forum.proxmox.com/threads/118492/post-513743
>
> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
>
> I just added it to the existing note, but maybe it's better to have
> two (one about existing guests, one about storage.cfg)? It still felt
> digestible like this and I wasn't entirely sure what to do about the
> sentence about the "configuration is overwritten"-sentence if opting
> to have two notes.
>
> pvecm.adoc | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
>
applied, thanks!
prev parent reply other threads:[~2023-01-16 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 14:09 [pve-devel] " Fiona Ebner
2023-01-16 15:55 ` Thomas Lamprecht [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=03f87272-dc10-2fe6-a176-22dfff324142@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@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