From: Vincent Batts <vbatts@hashbangbash.com>
To: linux-btrfs@vger.kernel.org
Cc: Vincent Batts <vbatts@hashbangbash.com>
Subject: [PATCH] btrfs-progs: subvolume verbose delete flag
Date: Thu, 15 Sep 2016 15:15:50 -0400 [thread overview]
Message-ID: <20160915191550.12371-2-vbatts@hashbangbash.com> (raw)
In-Reply-To: <20160915191550.12371-1-vbatts@hashbangbash.com>
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
next prev parent reply other threads:[~2016-09-15 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 19:15 [PATCH] Expose verbose flag on subvolume delete Vincent Batts
2016-09-15 19:15 ` Vincent Batts [this message]
2016-09-19 17:41 ` [PATCH] btrfs-progs: subvolume verbose delete flag David Sterba
2016-09-23 18:19 ` Vincent Batts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160915191550.12371-2-vbatts@hashbangbash.com \
--to=vbatts@hashbangbash.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).