linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Disseldorp <ddiss@suse.de>
To: linux-btrfs@vger.kernel.org
Cc: David Disseldorp <ddiss@suse.de>
Subject: [PATCH v2] btrfs-progs: fix typo in subvol list usage
Date: Mon, 18 Aug 2014 12:22:35 +0200	[thread overview]
Message-ID: <1408357355-15053-1-git-send-email-ddiss@suse.de> (raw)
In-Reply-To: <1397669690-11950-1-git-send-email-ddiss@suse.de>

Signed-off-by: David Disseldorp <ddiss@suse.de>
---
 Documentation/btrfs-subvolume.txt | 2 +-
 cmds-subvolume.c                  | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/btrfs-subvolume.txt b/Documentation/btrfs-subvolume.txt
index a519131..c8b9928 100644
--- a/Documentation/btrfs-subvolume.txt
+++ b/Documentation/btrfs-subvolume.txt
@@ -99,7 +99,7 @@ print the ogeneration of the subvolume, aliases: ogen or origin generation.
 -g::::
 print the generation of the subvolume.
 -o::::
-print only subvolumes bellow specified <path>.
+print only subvolumes below the specified <path>.
 -u::::
 print the UUID of the subvolume.
 -q::::
diff --git a/cmds-subvolume.c b/cmds-subvolume.c
index 5e821c7..75a7385 100644
--- a/cmds-subvolume.c
+++ b/cmds-subvolume.c
@@ -390,7 +390,7 @@ static const char * const cmd_subvol_list_usage[] = {
 	"             to the given <path>",
 	"-c           print the ogeneration of the subvolume",
 	"-g           print the generation of the subvolume",
-	"-o           print only subvolumes bellow specified path",
+	"-o           print only subvolumes below the specified path",
 	"-u           print the uuid of subvolumes (and snapshots)",
 	"-q           print the parent uuid of the snapshots",
 	"-t           print the result as a table",
-- 
1.8.4.5


      reply	other threads:[~2014-08-18 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 17:34 [PATCH] btrfs-progs: fix typo in subvol list usage David Disseldorp
2014-08-18 10:22 ` David Disseldorp [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=1408357355-15053-1-git-send-email-ddiss@suse.de \
    --to=ddiss@suse.de \
    --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).