All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <esandeen@redhat.com>
To: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Cc: Eric Sandeen <sandeen@redhat.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 1/3] btrfs-progs: random fixes of btrfs-filesystem documentation
Date: Mon, 11 Aug 2014 20:07:15 -0400 (EDT)	[thread overview]
Message-ID: <6DC8BDFA-32FF-4EB4-87D4-AB09F7A5A9FE@redhat.com> (raw)
In-Reply-To: <53E95703.9050705@jp.fujitsu.com>



> On Aug 11, 2014, at 4:51 PM, Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com> wrote:
> 
> Hi Eric,
> 
...
> 
> 
> OK, I'll fix my patch based on your comment.
> # Of course, I'll replace "(btrfs?)" with something proper words.

I assumed it only scans btrfs but didn't know for sure :)

> Can I add your "Signed-off-by" to my v2 patch?

Oh, sure, if you use my text, that makes sense.

thanks,
-Eric


>> 
>> (What seems to be missing, though, is why would the user ever choose to use '-d?')
> 
> I'm not sure. I guess, for example, in large systems, -d takes too
> many times for scanning all devices under /dev or something?
> 
> Thank you for your comments!
> 
> Satoru
> 
>> 
>> -Eric
> 

  reply	other threads:[~2014-08-12  0:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11  9:11 [PATCH 1/3] btrfs-progs: random fixes of btrfs-filesystem documentation Satoru Takeuchi
2014-08-11 17:05 ` Eric Sandeen
2014-08-11 17:14   ` Eric Sandeen
2014-08-11 23:55     ` Satoru Takeuchi
2014-08-11 23:51   ` Satoru Takeuchi
2014-08-12  0:07     ` Eric Sandeen [this message]
2014-08-12  7:25       ` [PATCH 1/3 v2] " Satoru Takeuchi
2014-08-12  7:45         ` [PATCH 1/3 v3] " Satoru Takeuchi
2014-08-12  8:06           ` [PATCH 1/3 v4] " Satoru Takeuchi
2014-08-19 15:07             ` David Sterba
2014-08-19 15:10   ` [PATCH 1/3] " David Sterba
2014-08-19 15:33     ` Eric Sandeen
2014-08-20 13:22       ` 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=6DC8BDFA-32FF-4EB4-87D4-AB09F7A5A9FE@redhat.com \
    --to=esandeen@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=takeuchi_satoru@jp.fujitsu.com \
    /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.