From: Fiona Ebner <f.ebner@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: [pve-devel] applied: [PATCH storage] btrfs: fix handling of non-images volumes
Date: Wed, 11 Dec 2024 15:01:01 +0100 [thread overview]
Message-ID: <8a3dfeb6-e35e-4111-8b9a-87555b2b361a@proxmox.com> (raw)
In-Reply-To: <20241211134836.2189515-1-f.gruenbichler@proxmox.com>
Am 11.12.24 um 14:48 schrieb Fabian Grünbichler:
> previously, only 'images' returned a format, now other volume types do too, so
> differentiate where needed.
>
> reported on the forum: https://forum.proxmox.com/threads/158888/
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
applied, thanks for the quick fix!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-12-11 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 13:48 [pve-devel] " Fabian Grünbichler
2024-12-11 14:01 ` 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=8a3dfeb6-e35e-4111-8b9a-87555b2b361a@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=f.gruenbichler@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