From: Vincent Batts <vbatts@hashbangbash.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: subvolume verbose delete flag
Date: Fri, 23 Sep 2016 14:19:10 -0400 [thread overview]
Message-ID: <20160923181910.GA29785@bananaboat.hashbangbash.com> (raw)
In-Reply-To: <20160919174149.GP16983@twin.jikos.cz>
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?
prev parent reply other threads:[~2016-09-23 18:19 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 ` [PATCH] btrfs-progs: subvolume verbose delete flag Vincent Batts
2016-09-19 17:41 ` David Sterba
2016-09-23 18:19 ` Vincent Batts [this message]
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=20160923181910.GA29785@bananaboat.hashbangbash.com \
--to=vbatts@hashbangbash.com \
--cc=dsterba@suse.cz \
--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).