All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs-progs: correct manpage option description for scrub
Date: Wed, 30 Jul 2014 10:26:38 +0000 (UTC)	[thread overview]
Message-ID: <pan$8f01a$5c9518b2$fccdda79$5ac3b72c@cox.net> (raw)
In-Reply-To: 1406705525-349-1-git-send-email-guihc.fnst@cn.fujitsu.com

Gui Hecheng posted on Wed, 30 Jul 2014 15:32:05 +0800 as excerpted:

> Also, add description of the potential failure as follows
>     "If a scrub is already running running, it fails."

Just a typo (running running?) in the description...

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2014-07-30 10:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17  2:40 [PATCH 1/4] btrfs-progs: adjust the return values for scrub Gui Hecheng
2014-07-17  2:40 ` [PATCH 2/4] btrfs-progs: remove unnecessary judgment for fd in scrub Gui Hecheng
2014-07-30  6:07   ` Satoru Takeuchi
2014-07-17  2:40 ` [PATCH 3/4] btrfs-progs: replace a confusing raw number with a macro Gui Hecheng
2014-07-29 12:16   ` David Sterba
2014-07-29 12:19     ` David Sterba
2014-07-30  1:17       ` Gui Hecheng
2014-07-17  2:40 ` [PATCH 4/4] btrfs-progs: correct manpage option description for scrub Gui Hecheng
2014-07-30  5:20   ` Satoru Takeuchi
2014-07-30  5:39     ` Gui Hecheng
2014-07-30  6:09       ` Satoru Takeuchi
2014-07-30  7:32         ` [PATCH v2] " Gui Hecheng
2014-07-30 10:26           ` Duncan [this message]
2014-07-31  1:25             ` Gui Hecheng
2014-07-31 12:24               ` David Sterba
2014-07-30  6:03 ` [PATCH 1/4] btrfs-progs: adjust the return values " Satoru Takeuchi
2014-07-30  6:36   ` Satoru Takeuchi
2014-07-30  7:27     ` Gui Hecheng

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='pan$8f01a$5c9518b2$fccdda79$5ac3b72c@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.