[pve-devel] [PATCH access-control] pveum: introduce sub-commands

2018-05-04 Thread Thomas Lamprecht
From: Philip Abernethy use a sub-command structure instead of abbreviated words, where useful. Keep old commands as aliases. Signed-off-by: Philip Abernethy Co-authored-by: Thomas Lamprecht --- Long over due, just found out this was not pushed yet. PVE/CLI/pveum.pm | 41

Re: [pve-devel] [PATCH access-control] pveum: introduce sub-commands

2017-10-10 Thread Philip Abernethy
On Tue, Oct 10, 2017 at 04:04:26PM +0200, Thomas Lamprecht wrote: > Thanks for this, useful to test the other patches. > > I am yet in the process of looking at the code changes but tested > a bit around. I noticed three problems: > > * when using the `help --verbose` command, e.g.,: > pveum help

Re: [pve-devel] [PATCH access-control] pveum: introduce sub-commands

2017-10-10 Thread Thomas Lamprecht
Thanks for this, useful to test the other patches. I am yet in the process of looking at the code changes but tested a bit around. I noticed three problems: * when using the `help --verbose` command, e.g.,: pveum help --verbose All but the first `USAGE: ...` strings are intended, which wasn't th

[pve-devel] [PATCH access-control] pveum: introduce sub-commands

2017-10-09 Thread Philip Abernethy
use a sub-command structure instead of abbreviated words, where useful. Keep old commands as aliases. --- In case the sub-commands patch gets applied, here is the first use case. PVE/CLI/pveum.pm | 41 ++--- 1 file changed, 30 insertions(+), 11 deletions(-) di