From: Ilya Dryomov <idryomov@gmail.com>
To: Anand jain <Anand.Jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs-progs: btrfs subvolume delete could delete subvolumes
Date: Fri, 21 Sep 2012 11:14:47 +0300 [thread overview]
Message-ID: <20120921081447.GA1961@zambezi.lan> (raw)
In-Reply-To: <1348210448-29616-1-git-send-email-Anand.Jain@oracle.com>
On Fri, Sep 21, 2012 at 02:54:08PM +0800, Anand jain wrote:
> From: Anand Jain <anand.jain@oracle.com>
>
> With this user will be able to provide more than one subvolume
> to delete.
> eg: btrfs subvolume delete <subvol1> <subvol2>
>
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
> cmds-subvolume.c | 36 ++++++++++++++++++++++++------------
> man/btrfs.8.in | 4 ++--
> 2 files changed, 26 insertions(+), 14 deletions(-)
>
> diff --git a/cmds-subvolume.c b/cmds-subvolume.c
> index f4aa80f..cfeaa8d 100644
> --- a/cmds-subvolume.c
> +++ b/cmds-subvolume.c
> @@ -188,31 +188,34 @@ int test_issubvolume(char *path)
> }
>
> static const char * const cmd_subvol_delete_usage[] = {
> - "btrfs subvolume delete <name>",
> - "Delete a subvolume",
> + "btrfs subvolume delete <subvolume> [<subvolume>...]",
> + "Delete subvolume(s)",
> NULL
> };
>
> static int cmd_subvol_delete(int argc, char **argv)
> {
> - int res, fd, len, e;
> + int res, fd, len, e, cnt = 1, ret = 0;
> struct btrfs_ioctl_vol_args args;
> char *dname, *vname, *cpath;
> char *path;
>
> - if (check_argc_exact(argc, 2))
> + if (argc < 2)
> usage(cmd_subvol_delete_usage);
check_argc_min(argc, 2)
Haven't looked at the rest.
Thanks,
Ilya
next prev parent reply other threads:[~2012-09-21 8:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 6:54 [PATCH] Btrfs-progs: btrfs subvolume delete could delete subvolumes Anand jain
2012-09-21 8:14 ` Ilya Dryomov [this message]
2012-09-24 2:46 ` [PATCH v2] " Anand jain
2012-09-21 15:20 ` [PATCH] " David Sterba
2012-09-24 2:59 ` Anand Jain
2012-09-24 12:02 ` David Sterba
2012-09-24 14:36 ` cwillu
2012-09-30 23:17 ` David Sterba
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=20120921081447.GA1961@zambezi.lan \
--to=idryomov@gmail.com \
--cc=Anand.Jain@oracle.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).