* [PATCH] Expose verbose flag on subvolume delete @ 2016-09-15 19:15 Vincent Batts 2016-09-15 19:15 ` [PATCH] btrfs-progs: subvolume verbose delete flag Vincent Batts 0 siblings, 1 reply; 4+ messages in thread From: Vincent Batts @ 2016-09-15 19:15 UTC (permalink / raw) To: linux-btrfs; +Cc: Vincent Batts Exposing the verbose flag that already had the logic for verbose output Vincent Batts (1): btrfs-progs: subvolume verbose delete flag cmds-subvolume.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) -- 2.9.0 ^ permalink raw reply [flat|nested] 4+ messages in thread
* [PATCH] btrfs-progs: subvolume verbose delete flag 2016-09-15 19:15 [PATCH] Expose verbose flag on subvolume delete Vincent Batts @ 2016-09-15 19:15 ` Vincent Batts 2016-09-19 17:41 ` David Sterba 0 siblings, 1 reply; 4+ messages in thread From: Vincent Batts @ 2016-09-15 19:15 UTC (permalink / raw) To: linux-btrfs; +Cc: Vincent Batts There was already the logic for verbose output, but the flag parsing did not include it. Signed-off-by: Vincent Batts <vbatts@hashbangbash.com> --- cmds-subvolume.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/cmds-subvolume.c b/cmds-subvolume.c index e7ef67d..f8c9f48 100644 --- a/cmds-subvolume.c +++ b/cmds-subvolume.c @@ -245,6 +245,7 @@ static const char * const cmd_subvol_delete_usage[] = { "", "-c|--commit-after wait for transaction commit at the end of the operation", "-C|--commit-each wait for transaction commit after deleting each subvolume", + "-v|--verbose verbose output of operations", NULL }; @@ -267,10 +268,11 @@ static int cmd_subvol_delete(int argc, char **argv) static const struct option long_options[] = { {"commit-after", no_argument, NULL, 'c'}, /* commit mode 1 */ {"commit-each", no_argument, NULL, 'C'}, /* commit mode 2 */ + {"verbose", no_argument, NULL, 'v'}, {NULL, 0, NULL, 0} }; - c = getopt_long(argc, argv, "cC", long_options, NULL); + c = getopt_long(argc, argv, "cCv", long_options, NULL); if (c < 0) break; -- 2.9.0 ^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH] btrfs-progs: subvolume verbose delete flag 2016-09-15 19:15 ` [PATCH] btrfs-progs: subvolume verbose delete flag Vincent Batts @ 2016-09-19 17:41 ` David Sterba 2016-09-23 18:19 ` Vincent Batts 0 siblings, 1 reply; 4+ messages in thread From: David Sterba @ 2016-09-19 17:41 UTC (permalink / raw) To: Vincent Batts; +Cc: linux-btrfs On Thu, Sep 15, 2016 at 03:15:50PM -0400, Vincent Batts wrote: > There was already the logic for verbose output, but the flag parsing did > not include it. > > Signed-off-by: Vincent Batts <vbatts@hashbangbash.com> Applied, thanks. I wonder where the original argument got lost. In the commit 2ed161bd281beca29feebebbc8c4227cc6e918c3 it to added to getopt but inside cmd_subvol_create. I'll fix it as well. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] btrfs-progs: subvolume verbose delete flag 2016-09-19 17:41 ` David Sterba @ 2016-09-23 18:19 ` Vincent Batts 0 siblings, 0 replies; 4+ messages in thread From: Vincent Batts @ 2016-09-23 18:19 UTC (permalink / raw) To: dsterba, linux-btrfs On 19/09/16 19:41 +0200, David Sterba wrote: >Applied, thanks. I wonder where the original argument got lost. In the >commit 2ed161bd281beca29feebebbc8c4227cc6e918c3 it to added to getopt >but inside cmd_subvol_create. I'll fix it as well. Not sure. I found it while investigating feasibility of adding a flag to recursively delete subvolumes. Which, do you have particular feelings about recursive deletes? ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-09-23 18:19 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2016-09-15 19:15 [PATCH] Expose verbose flag on subvolume delete Vincent Batts 2016-09-15 19:15 ` [PATCH] btrfs-progs: subvolume verbose delete flag Vincent Batts 2016-09-19 17:41 ` David Sterba 2016-09-23 18:19 ` Vincent Batts
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).