From: Mike Fedyk <mfedyk@mikefedyk.com>
To: Goffredo Baroncelli <kreijack@gmail.com>
Cc: linux-btrfs@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: Re: [PATCH 0/2] btrfs: a new tool to manage a btrfs filesystem
Date: Fri, 12 Feb 2010 11:32:15 -0800 [thread overview]
Message-ID: <93cdabd21002121132w5d6e543bpa4147066345201aa@mail.gmail.com> (raw)
In-Reply-To: <201002122001.09898.kreijack@libero.it>
On Fri, Feb 12, 2010 at 11:01 AM, Goffredo Baroncelli
<kreijack@gmail.com> wrote:
> Usage:
> =C2=A0 =C2=A0 =C2=A0 =C2=A0btrfs delete|-D <subvolume>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Delete the sub=
volume <subvolume>.
> =C2=A0 =C2=A0 =C2=A0 =C2=A0btrfs defrag|-d <file>|<dir> [<file>|<dir>=
=2E..]
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Defragment a f=
ile or a directory.
I think the short options should be removed or else you'll still have
the easy misuses of btrfs -d and btrfs -D.
The best example would be the "ip" command which has commands and
-[a-z] options that do different types of things. for instance, all
of the short options are applicable to all commands and change the
verbosity or format of the output.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-02-12 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 19:01 [PATCH 0/2] btrfs: a new tool to manage a btrfs filesystem Goffredo Baroncelli
2010-02-12 19:32 ` Mike Fedyk [this message]
2010-08-29 18:38 ` btrfs-progs: error in manage Andreas Philipp
-- strict thread matches above, loose matches on Subject: below --
2010-02-14 10:17 [PATCH 0/2] btrfs: a new tool to manage a btrfs filesystem Thomas Kupper
2010-02-14 12:54 ` Dipl.-Ing. Michael Niederle
2010-02-14 15:39 ` Goffredo Baroncelli
2010-02-16 17:31 ` Mike Fedyk
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=93cdabd21002121132w5d6e543bpa4147066345201aa@mail.gmail.com \
--to=mfedyk@mikefedyk.com \
--cc=chris.mason@oracle.com \
--cc=kreijack@gmail.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).