From: Friedrich Weber <f.weber@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] applied: [RFC storage] content-dirs: check that all content dirs are pairwise inequal
Date: Wed, 7 Jun 2023 09:46:48 +0200 [thread overview]
Message-ID: <542502fa-f937-143a-022d-30665fd969a7@proxmox.com> (raw)
In-Reply-To: <9037eaa6-7fe5-41db-1cf0-3cd19548e562@proxmox.com>
On 06/06/2023 17:28, Thomas Lamprecht wrote:
> Well, then lets apply this for upcoming 8, maybe you can add a note to
> our breaking changes list so that users are aware.
Done!
> Also, checking this upfront and erroring in pve7to8 checker script should
> not be that hard and def. help some to avoid problems during/after the
> upgrade.
Yes, sounds sensible. I'll prepare a patch.
next prev parent reply other threads:[~2023-06-07 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 17:03 [pve-devel] " Friedrich Weber
2023-06-06 15:28 ` [pve-devel] applied: " Thomas Lamprecht
2023-06-07 7:46 ` Friedrich Weber [this message]
2023-06-07 10:01 ` [pve-devel] " Fiona Ebner
2023-06-07 10:18 ` Friedrich Weber
2023-06-07 10:35 ` 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=542502fa-f937-143a-022d-30665fd969a7@proxmox.com \
--to=f.weber@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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