From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Arthur Othieno <a.othieno@bluewin.ch>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/2] VFS: update overview document
Date: Sat, 29 Oct 2005 10:35:41 +0300 [thread overview]
Message-ID: <1130571341.7965.2.camel@localhost> (raw)
In-Reply-To: <20051028200752.GB25468@krypton>
Hi,
On Fri, 2005-10-28 at 16:07 -0400, Arthur Othieno wrote:
> How about splitting the API stuff into include/linux/fs.h as kerneldoc?
> That way, it gets updated as well when the interface changes, and keeps
> Documetation/DocBook/kernel-api.tmpl looking shiny new..
I have been thinking about this as well. My first priority is to bring
the document up to date, though.
Pekka
prev parent reply other threads:[~2005-10-29 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 15:48 [PATCH 1/2] VFS: update overview document Pekka Enberg
2005-10-28 15:48 ` [PATCH 2/2] VFS: split dentry locking documentation Pekka Enberg
2005-10-28 20:07 ` [PATCH 1/2] VFS: update overview document Arthur Othieno
2005-10-29 7:35 ` Pekka Enberg [this message]
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=1130571341.7965.2.camel@localhost \
--to=penberg@cs.helsinki.fi \
--cc=a.othieno@bluewin.ch \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox