Linux Btrfs filesystem development
 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] btrfs-progs: check: add experimental flag for lowmem mode
Date: Tue,  3 Jul 2018 13:42:37 +0200	[thread overview]
Message-ID: <20180703114237.11053-1-ddiss@suse.de> (raw)

The experimental flag is already carried in the manpage, but was removed
from the btrfs check usage message as part of refactoring via
87c1bd13c1fca430c3dbf0da62e9aa33bde609c8. Add it back.

Signed-off-by: David Disseldorp <ddiss@suse.de>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
---
 check/main.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/check/main.c b/check/main.c
index 3190b5d4..9aca0c09 100644
--- a/check/main.c
+++ b/check/main.c
@@ -9386,7 +9386,7 @@ const char * const cmd_check_usage[] = {
 	"                            original - read inodes and extents to memory (requires",
 	"                                       more memory, does less IO)",
 	"                            lowmem   - try to use less memory but read blocks again",
-	"                                       when needed",
+	"                                       when needed (experimental)",
 	"--check-data-csum           verify checksums of data blocks",
 	"-Q|--qgroup-report          print a report on qgroup consistency",
 	"-E|--subvol-extents <subvolid>",
-- 
2.13.7


             reply	other threads:[~2018-07-03 11:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03 11:42 David Disseldorp [this message]
2018-07-04  1:19 ` [PATCH] btrfs-progs: check: add experimental flag for lowmem mode Su Yue
2018-07-04 11:55 ` 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=20180703114237.11053-1-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