[pve-devel] pve-storage : volume_lock && volume_unlock
Alexandre DERUMIER
aderumier at odiso.com
Mon Dec 3 11:14:38 CET 2012
>>It would be cool if we have these git repos public containing new
>>features / work in progress ideas.
>>
>>What about mirroring to github and working there with Feature branches?
Why not. Does Dietmar agree with this ?
----- Mail original -----
De: "Stefan Priebe - Profihost AG" <s.priebe at profihost.ag>
À: pve-devel at pve.proxmox.com
Envoyé: Lundi 3 Décembre 2012 09:23:46
Objet: Re: [pve-devel] pve-storage : volume_lock && volume_unlock
Hi Alexandre,
Am 03.12.2012 08:53, schrieb Alexandre DERUMIER:
>>> I think you should not use the term 'lock/unlock' here.
>>>
>>> Maybe something like:
>>>
>>> volume_protect(true/false)
>
> volume_protect seem good. (as snapshot are not really readonly, and rbd already use protect for the rbd command)
>
> I'll change that in my git.
It would be cool if we have these git repos public containing new
features / work in progress ideas.
What about mirroring to github and working there with Feature branches?
Greets,
Stefan
_______________________________________________
pve-devel mailing list
pve-devel at pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
More information about the pve-devel
mailing list