On 4/8/25 17:34, Thomas Lamprecht wrote:
Am 08.04.25 um 14:13 schrieb Dominik Csapak:
By enabling the import button for qcow2/vmdk/raw files, and showing a
window with a VMID selector and the disk edit panel.
functionality wise I'd have applied that as it would be new and have thus
almost no regression potential, might be also better to factor out the
panel upfront in a dedicated commit and then integrate it everywhere.
But lets wait this out, no point in rushing things here.
Sure, don't rush this. Is there anything concrete you'd want to do have done
differently
here though?
Even for the import storage content I'd really like to reuse the general disk
edit panel
(for e.g. the detection of which bus/controller is used, etc.), so the
regression potential
would be no different even if we'd only show it in the storage content.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
