From: Marc Koschewski <marc@osknowledge.org>
To: 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 18:34:05 +0100 [thread overview]
Message-ID: <20051121173404.GA7886@stiffy.osknowledge.org> (raw)
In-Reply-To: <1132538219.5706.36.camel@localhost.localdomain>
* 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.
Marc
next prev parent reply other threads:[~2005-11-21 17:33 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 [this message]
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
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=20051121173404.GA7886@stiffy.osknowledge.org \
--to=marc@osknowledge.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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