public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH storage v2 1/5] plugin: fix typo in rebase log message
Date: Tue, 29 Jul 2025 14:15:44 +0200	[thread overview]
Message-ID: <1753791276.r2g4o2fl20.astroid@yuna.none> (raw)
In-Reply-To: <ce1f94c5-726b-4060-a63d-2b9ec32af384@proxmox.com>

On July 29, 2025 2:04 pm, Fiona Ebner wrote:
> Am 29.07.25 um 1:53 PM schrieb Fabian Grünbichler:
>> by directly printing the to-be-executed command, instead of copying it which is
>> error-prone.
>> 
>> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
>> Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>
>> ---
>> 
>> Notes:
>>     v2: join command instead of fixing manually copied message
>> 
>>  src/PVE/Storage/Plugin.pm | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>> 
>> diff --git a/src/PVE/Storage/Plugin.pm b/src/PVE/Storage/Plugin.pm
>> index 2bd05bd..de41bfe 100644
>> --- a/src/PVE/Storage/Plugin.pm
>> +++ b/src/PVE/Storage/Plugin.pm
>> @@ -1437,7 +1437,6 @@ sub volume_snapshot_delete {
>>              my $parentpath = $snapshots->{$parentsnap}->{file};
>>              print
>>                  "$volname: deleting snapshot '$snap' by rebasing '$childsnap' on top of '$parentsnap'\n";
>> -            print "running 'qemu-img rebase -b $parentpath -F qcow -f qcow2 $childpath'\n";
>>              $cmd = [
>>                  '/usr/bin/qemu-img',
>>                  'rebase',
>> @@ -1449,6 +1448,7 @@ sub volume_snapshot_delete {
>>                  'qcow2',
>>                  $childpath,
>>              ];
>> +            print "running '", join(' ', $cmd->@*), "'\n";
> 
> Style nit: we usually do concatenation with dot, was using commas for
> passing a list to print intentional? Same for the next patch.

force of habit, no real reason - feel free to fixup on applying :)

>>              eval { run_command($cmd) };
>>              if ($@) {
>>                  #in case of abort, the state of the snap is still clean, just a little bit bigger
> 
> 


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  reply	other threads:[~2025-07-29 12:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-29 11:53 [pve-devel] [PATCH storage/qemu-server v2 0/5] avoid absolute qcow2 references Fabian Grünbichler
2025-07-29 11:53 ` [pve-devel] [PATCH storage v2 1/5] plugin: fix typo in rebase log message Fabian Grünbichler
2025-07-29 12:04   ` Fiona Ebner
2025-07-29 12:15     ` Fabian Grünbichler [this message]
2025-07-29 11:53 ` [pve-devel] [PATCH storage v2 2/5] lvm " Fabian Grünbichler
2025-07-29 11:53 ` [pve-devel] [PATCH storage v2 3/5] plugin: use relative path for qcow2 rebase command Fabian Grünbichler
2025-07-29 11:53 ` [pve-devel] [PATCH storage v2 4/5] lvm " Fabian Grünbichler
2025-07-29 11:53 ` [pve-devel] [PATCH qemu-server v2 5/5] blockdev-stream/-commit: make backing file relative Fabian Grünbichler
2025-07-29 12:51 ` [pve-devel] applied-series: [PATCH storage/qemu-server v2 0/5] avoid absolute qcow2 references Fiona Ebner

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=1753791276.r2g4o2fl20.astroid@yuna.none \
    --to=f.gruenbichler@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal