From: Scott Lovenberg <scott.lovenberg@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Documentation about sysfs/procfs entries]
Date: Wed, 13 Feb 2008 01:05:06 -0500 [thread overview]
Message-ID: <47B28892.2010500@gmail.com> (raw)
Randy Dunlap wrote:
> On Wed, 13 Feb 2008 09:08:12 +0700 Mulyadi Santosa wrote:
>
>
>> Hi all...
>>
>> Here's my idea: what if we collaborate to extend and make the kernel
>> documentation better? I have done (slow) start by editing profile=
>> kernel param. It's not accepted by Adrian Bunk, but at least I did it.
>> Feedback?
>>
>
> Adrian is no longer the trivial patch maintainer.
> Did you send the patch to trivial@kernel.org ?
>
> Any doc additions or improvements would be appreciated.
> I'll be glad to help get them merged...
>
> ---
> ~Randy
>
>
I'd love to help, but I'm a bit of a newbie; what's protocol for
documentation updates, standard diffs?
How are we going to attack this thing, cleaning up and updating existing
documentation first and then adding undocumented items, or file by file
updating and adding in one fell swoop?
At any rate, I'm in.
Hopefully this will turn out better than the last time I said those
words and woke up in Mexico with a new tattoo and without my pants. :)
reply other threads:[~2008-02-13 6:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47B28892.2010500@gmail.com \
--to=scott.lovenberg@gmail.com \
--cc=linux-kernel@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.