From: Kent Overstreet <kent.overstreet@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] bcache: ver 3
Date: Fri, 23 Apr 2010 12:46:06 -0800 [thread overview]
Message-ID: <4BD2070E.5060103@gmail.com> (raw)
In-Reply-To: <4BD200BB.1070709@oracle.com>
On 04/23/2010 12:19 PM, Randy Dunlap wrote:
> On 04/23/10 13:17, Kent Overstreet wrote:
>> On 04/23/2010 12:07 PM, Randy Dunlap wrote:
>>> help
>>> <some explanatory help text>
>>> please. The tristate prompt didn't do anything for me.
>>
>> Did the prompt not show up at all? That's odd, I wouldn't have thought
>> help text would have anything to do with that - I just added help to the
>> kconfig, though. I'll have it up in a git repository soon, I don't
>> suppose I should be posting a 2.4k line patch multiple times per day...
>
> I'm just saying that it needs help text -- the prompt doesn't say enough.
>
Ah, right. It still needs real documentation in general, that should probably
be a higher priority.
(Somewhat messy, will be rewritten) repo is up at
http://modzer0.cs.uaf.edu/~kent/linux-bcache.git, kconfig help is in. If
there's something in particular you think ought to be documented for
understanding the code, I'll do that now. End user documentation I was
planning on waiting a bit on as I'm sure stuff is going to have to change.
next prev parent reply other threads:[~2010-04-23 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 19:41 [RFC][PATCH] bcache: ver 3 Kent Overstreet
2010-04-23 20:07 ` Randy Dunlap
2010-04-23 20:17 ` Kent Overstreet
2010-04-23 20:19 ` Randy Dunlap
2010-04-23 20:46 ` Kent Overstreet [this message]
2010-04-23 20:39 ` Randy Dunlap
2010-04-23 21:05 ` Kent Overstreet
2010-04-25 11:48 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2010-04-24 15:47 Egon Alter
2010-04-24 20:08 ` Kent Overstreet
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=4BD2070E.5060103@gmail.com \
--to=kent.overstreet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox