From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Maximiliano Sandoval <m.sandoval@proxmox.com>,
PVE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH storage v2] fix-4272: btrfs: add rename feature
Date: Thu, 4 Jul 2024 12:01:36 +0200 [thread overview]
Message-ID: <1fc07621-6939-42f6-9749-293355d4d3a6@proxmox.com> (raw)
In-Reply-To: <s8osewp5w88.fsf@proxmox.com>
CC'ing pve-devel again.
Am 04/07/2024 um 11:42 schrieb Maximiliano Sandoval:
> Thomas Lamprecht <t.lamprecht@proxmox.com> writes:
>> Am 03/07/2024 um 14:41 schrieb Maximiliano Sandoval:
>>> Adds the ability to change the owner of a guest image.
>>>
>>> Btrfs does not need special commands to rename a subvolume and this can
>>> be achieved the same as in Storage/plugin.pm's rename_volume taking
>>> special care of how the directory structure used by Btrfs.
>>>
>>> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
>>> ---
>>
>> this missing a v1 -> v2 changelog here.
>
> Right.
>
> The changelog is basically:
>
> Differences from v1:
> - Rename unused variables to undef
>
Thanks for providing one, it's also very important for small/trivial
changes, as then one can know that the basics did not change, which allows
one to spent less time on reviewing the whole thing.
The changelog might be slightly easier to understand, at least to me, if
worded:
- avoid assigning unused values of returned list to variables
btw. one should be also able to do something like:
my $format = ($class->parse_volname($source_volname))[6];
here.
While not perfect, that would be IMO not really be worse than having 5
undef's bloating up code line in this case.
Orthogonal to this: adding a "parse_volume_format" (wrapper) method to
the storage plugin might really be worth it, as IIRC we have this use case
on quite a few places. But that certainly does not need to happen before
this patch.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-07-04 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 12:41 Maximiliano Sandoval
2024-07-04 9:32 ` Thomas Lamprecht
[not found] ` <s8osewp5w88.fsf@proxmox.com>
2024-07-04 10:01 ` Thomas Lamprecht [this message]
2024-07-04 9:49 ` Fiona Ebner
2024-07-04 9:52 ` Aaron Lauterer
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=1fc07621-6939-42f6-9749-293355d4d3a6@proxmox.com \
--to=t.lamprecht@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.