linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: chris.mason@fusionio.com
Subject: [PATCH 4/5] Btrfs-progs: cleanup btrfs-image usage
Date: Sat, 22 Jun 2013 13:32:44 +0800	[thread overview]
Message-ID: <1371879165-4993-5-git-send-email-bo.li.liu@oracle.com> (raw)
In-Reply-To: <1371879165-4993-1-git-send-email-bo.li.liu@oracle.com>

A '\n' is missing.

Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
---
 btrfs-image.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/btrfs-image.c b/btrfs-image.c
index 30c1a9a..ebd283e 100644
--- a/btrfs-image.c
+++ b/btrfs-image.c
@@ -2272,7 +2272,7 @@ static void print_usage(void)
 	fprintf(stderr, "\t-c value\tcompression level (0 ~ 9)\n");
 	fprintf(stderr, "\t-t value\tnumber of threads (1 ~ 32)\n");
 	fprintf(stderr, "\t-o      \tdon't mess with the chunk tree when restoring\n");
-	fprintf(stderr, "\t-s      \tsanitize file names, use once to just use garbage, use twice if you want crc collisions");
+	fprintf(stderr, "\t-s      \tsanitize file names, use once to just use garbage, use twice if you want crc collisions\n");
 	fprintf(stderr, "\t-w      \twalk all trees instead of using extent tree, do this if your extent tree is broken\n");
 	exit(1);
 }
-- 
1.7.7


  parent reply	other threads:[~2013-06-22  5:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-22  5:32 [PATCH 0/5 v2] multiple disks restore support of btrfs-image Liu Bo
2013-06-22  5:32 ` [PATCH 1/5] Btrfs-progs: fix misuse of skinny metadata in btrfs-image Liu Bo
2013-06-22  5:32 ` [PATCH 2/5] Btrfs-progs: skip open devices which is missing Liu Bo
2013-06-22  5:32 ` [PATCH 3/5] Btrfs-progs: delete fs_devices itself from fs_uuid list before freeing Liu Bo
2013-06-22  5:32 ` Liu Bo [this message]
2013-06-22  5:32 ` [PATCH 5/5 v2] Btrfs-progs: enhance btrfs-image to restore image onto multiple disks Liu Bo

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=1371879165-4993-5-git-send-email-bo.li.liu@oracle.com \
    --to=bo.li.liu@oracle.com \
    --cc=chris.mason@fusionio.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).