From: "Christopher Friesen" <cfriesen@nortel.com>
To: Rob Landley <rob@landley.net>
Cc: Xose Vazquez Perez <xose.vazquez@gmail.com>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Documentation dir is a mess
Date: Mon, 21 Nov 2005 13:22:03 -0600 [thread overview]
Message-ID: <43821E5B.3040307@nortel.com> (raw)
In-Reply-To: <200511211205.12861.rob@landley.net>
Rob Landley wrote:
> Except that I picked proc.txt because the contents of the file are really
> about the whole source tree. (This isn't documentation about the proc
> filesystem infrastructure, it's documentation about all known users of that
> infrastructure...)
This depends on how you're looking at it.
Documentation/filesystems/proc.txt is written from a "user" perspective,
not a "kernel developer" perspective.
From the user perspective, this file documents the contents of "/proc"
which is one single place.
Chris
next prev parent reply other threads:[~2005-11-21 19:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 12:19 [RFC] Documentation dir is a mess Xose Vazquez Perez
2005-11-21 0:30 ` Greg KH
2005-11-21 1:56 ` Steven Rostedt
2005-11-21 17:34 ` Marc Koschewski
2005-11-22 6:06 ` Matthew Frost
2005-11-22 9:18 ` Paul Jackson
2005-11-22 13:46 ` Steven Rostedt
2005-11-22 18:42 ` Paul Jackson
2005-11-22 9:56 ` Marc Koschewski
2005-11-25 19:53 ` [RFC PATCH] was " Xose Vazquez Perez
2005-11-21 16:28 ` Rob Landley
2005-11-21 16:44 ` Christopher Friesen
2005-11-21 18:05 ` Rob Landley
2005-11-21 19:22 ` Christopher Friesen [this message]
2005-11-21 16:46 ` Jiri Slaby
2005-11-25 20:27 ` Xose Vazquez Perez
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=43821E5B.3040307@nortel.com \
--to=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=rob@landley.net \
--cc=xose.vazquez@gmail.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.