need by my last pve-manager pending patches
I'm not sure, but maybe could we simply change /config api, to display pending
devices if they exist
___
pve-devel mailing list
pve-devel@pve.proxmox.com
need by my last pve-manager pending patches
I'm not sure, but maybe could we simply change /config api, to display pending
devices if they exist
Yes, I think that is a good idea.
Currently (with pending patches), the semantics of the config API changed, which
is bad.
Instead, I thought
?
- Mail original -
De: dietmar diet...@proxmox.com
À: aderumier aderum...@odiso.com, pve-devel pve-devel@pve.proxmox.com
Envoyé: Vendredi 19 Décembre 2014 12:23:32
Objet: Re: [pve-devel] qemu-server : add configpending api (for test)
need by my last pve-manager pending patches
I'm not sure
Instead, I thought about adding a new optional Boolean parameter called
'pending', used to include
pending changes. That way the config API remains stable.
Would you mind to adopt your patch?
Sure , no problem.
I'm not sure how to call the optionnal pending param in GET api url ?
I
Instead, I thought about adding a new optional Boolean parameter called
'pending', used to include
pending changes. That way the config API remains stable.
Would you mind to adopt your patch?
Sure , no problem.
I'm not sure how to call the optionnal pending param in GET api
: [pve-devel] qemu-server : add configpending api (for test)
Instead, I thought about adding a new optional Boolean parameter called
'pending', used to include
pending changes. That way the config API remains stable.
Would you mind to adopt your patch?
Sure , no problem.
I'm
