From: "Paul Drynoff" <pauldrynoff@gmail.com>
To: "Christoph Lameter" <clameter@sgi.com>
Cc: "Jesper Juhl" <jesper.juhl@gmail.com>,
"Pekka J Enberg" <penberg@cs.helsinki.fi>,
akpm@osdl.org, "Linus Torvalds" <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kmalloc man page before 2.6.17
Date: Fri, 26 May 2006 18:55:46 +0400 [thread overview]
Message-ID: <36e6b2150605260755t254e4850l2b69f72fe730279@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0605260714460.30772@schroedinger.engr.sgi.com>
On 5/26/06, Christoph Lameter <clameter@sgi.com> wrote:
> Documentation of in kernel functions in the manpages <boogle>.
Why not, this is common practic for big set of Unix lie OS.
You can type something like:
man VFS man vnops and so on.
> You are
> going to do this full time in order to keep all of it up to date?
>
> In that case you should add something to install the manpages
> for each kernel when one does
>
Why? In my Linux OS I should only type something like:
package-manager install vanilla-sources
or
package-manager install git-sources
and I'll get all documentation generated by "make mandocs" in
/usr/share/man/man9
next prev parent reply other threads:[~2006-05-26 14:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 7:07 Paul Drynoff
2006-05-26 7:17 ` Pekka Enberg
2006-05-26 7:58 ` Paul Drynoff
2006-05-26 8:03 ` Pekka J Enberg
2006-05-26 8:20 ` Paul Drynoff
2006-05-26 9:42 ` Andrey Panin
2006-05-26 9:48 ` Jesper Juhl
2006-05-26 10:44 ` Paul Drynoff
2006-05-26 13:23 ` Paulo Marques
2006-05-26 14:17 ` Christoph Lameter
2006-05-26 14:55 ` Paul Drynoff [this message]
2006-05-26 15:03 ` Christoph Lameter
2006-05-26 19:55 ` Luca
2006-05-27 10:28 ` Martin Waitz
2006-05-26 10:47 ` Paul Drynoff
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=36e6b2150605260755t254e4850l2b69f72fe730279@mail.gmail.com \
--to=pauldrynoff@gmail.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®