From: Matthew Frost <artusemrys@sbcglobal.net>
To: Marc Koschewski <marc@osknowledge.org>,
Steven Rostedt <rostedt@goodmis.org>
Cc: Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
"Randy.Dunlap" <rdunlap@xenotime.net>,
Xose Vazquez Perez <xose.vazquez@gmail.com>
Subject: Re: [RFC] Documentation dir is a mess
Date: Mon, 21 Nov 2005 22:06:48 -0800 (PST) [thread overview]
Message-ID: <20051122060648.8827.qmail@web81904.mail.mud.yahoo.com> (raw)
In-Reply-To: <20051121173404.GA7886@stiffy.osknowledge.org>
--- Marc Koschewski <marc@osknowledge.org> wrote:
> * Steven Rostedt <rostedt@goodmis.org> [2005-11-20 20:56:59 -0500]:
>
> > On Sun, 2005-11-20 at 16:30 -0800, Greg KH wrote:
> > > On Sun, Nov 20, 2005 at 01:19:09PM +0100, Xose Vazquez Perez wrote:
> > > > hi,
> > > >
> > > > _today_ Documentation/* is a mess of files. It would be good
> > > > to have the _same_ tree as the code has:
> > >
> > > Do you have a proposal as to what specific files in that directory
> > > should go where? Just basing it on the source tree will not get
> > > you very far...
> >
> > Actually I think it's a good start. When I'm looking for
> > documentation, I usually just do a grep -r on the Documentation
> > directory hoping I get a correct hit and then manually look
> > through all the results I get.
> > It does get tedious, and I miss things all the time.
>
> As you're just about to maybe make a decision on reorganisation: how
> about a separation of user- and developer-relevant documentation?
> I mean, kernel boot parameters are relevant to a user whereas
> mm/* stuff is not.
There's a problem in the general conception that user/developer is a
mutex. The whole idea is that anyone may become a developer at will. A
division of Documentation/ to make an artificial distinction that the
community doesn't necessarily believe in doesn't seem too useful.
Now, I don't mean to suggest that you're wrong; I'm sure you have a valid
point. If I may rephrase, it sounds more like you're looking for
"fingertip reference" versus "in-depth documentation". The documents
that exist may not conform themselves well to that sort of division,
necessarily. However, I'm sure that there exist fingertip references
outside of Documentation/ and the kernel tree; many of them are for
'newbies'.
Is this a useful interpretation? Would an incorporation of this sort of
functional division meet your request? Does anyone have the time to
devote to it? Am I just reading out of the bit bucket?
Matt
>
> Marc
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2005-11-22 6:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 12:19 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 [this message]
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
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=20051122060648.8827.qmail@web81904.mail.mud.yahoo.com \
--to=artusemrys@sbcglobal.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@osknowledge.org \
--cc=rdunlap@xenotime.net \
--cc=rostedt@goodmis.org \
--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 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®