From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Maximiliano Sandoval <m.sandoval@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH storage v4 1/7] btrfs: add helper to iterate over snapshots of a subvolume
Date: Mon, 24 Feb 2025 10:21:27 +0100 [thread overview]
Message-ID: <db782fff-d7e7-42d1-b662-1d40cacf845e@proxmox.com> (raw)
In-Reply-To: <20250219111740.200819-1-m.sandoval@proxmox.com>
Am 19.02.25 um 12:17 schrieb Maximiliano Sandoval:
> In this context a subvolume means a BTRFS subvolume.
> `$volume\@$snap_name` would be for example
> `btrfs_volume/images/102/vm-102-disk-0@snap_name`.
>
> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
applied series, thanks!
_______________________________________________
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-02-24 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 11:17 [pve-devel] " Maximiliano Sandoval
2025-02-19 11:17 ` [pve-devel] [PATCH storage v4 2/7] fix #3873: btrfs: use foreach_snapshot_of_subvol helper in volume_export Maximiliano Sandoval
2025-02-19 11:17 ` [pve-devel] [PATCH storage v4 3/7] btrfs: use foreach_snapshot_of_subvol helper in free_image Maximiliano Sandoval
2025-02-19 11:17 ` [pve-devel] [PATCH storage v4 4/7] btrfs: forcefully set image to readwrite Maximiliano Sandoval
2025-02-21 15:44 ` Fiona Ebner
2025-02-24 8:43 ` Maximiliano Sandoval
2025-02-19 11:17 ` [pve-devel] [PATCH storage v4 5/7] btrfs: rename volume regex Maximiliano Sandoval
2025-02-19 11:17 ` [pve-devel] [PATCH storage v4 6/7] btrfs: remove foreach_subvol Maximiliano Sandoval
2025-02-19 11:17 ` [pve-devel] [PATCH storage v4 7/7] btrfs: rename snapshot parameter Maximiliano Sandoval
2025-02-24 9:21 ` 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=db782fff-d7e7-42d1-b662-1d40cacf845e@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=m.sandoval@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