From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Nicolas Frey <n.frey@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-common v2] cli: fix #6762: only copy properties if defined
Date: Wed, 8 Oct 2025 21:41:52 +0200 [thread overview]
Message-ID: <175995251203.1422766.1559297246934990190.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251007151649.163255-1-n.frey@proxmox.com>
On Tue, 07 Oct 2025 17:16:49 +0200, Nicolas Frey wrote:
> Adds a defined check to the copy, as to not result in the following
> error:
>
> ~# pveceph status Can't use an undefined value as a HASH reference at
> /usr/share/perl5/PVE/CLIHandler.pm line 455, <DATA> line 960.
>
> Pressing double tab after status produces the above message.
>
> [...]
Applied, thanks!
[1/1] cli: fix #6762: only copy properties if defined
commit: dcf1836b6844976d60b71d0655b926cc1bdf2fe9
_______________________________________________
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-10-08 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 15:16 [pve-devel] " Nicolas Frey
2025-10-08 19:41 ` Thomas Lamprecht [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=175995251203.1422766.1559297246934990190.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=n.frey@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