From: Adrian Bunk <bunk@kernel.org>
To: Doug Thompson <norsk5@yahoo.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
dougthompson@xmission.com, bluesmoke-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] move edac.txt DOCUMENTATION two levels up
Date: Mon, 5 Nov 2007 20:14:00 +0100 [thread overview]
Message-ID: <20071105191400.GB3444@stusta.de> (raw)
In-Reply-To: <293742.55428.qm@web50101.mail.re2.yahoo.com>
On Mon, Nov 05, 2007 at 10:52:01AM -0800, Doug Thompson wrote:
> Interesting
>
> At the time I submitted it there was a big discussion on just how messed up the documentation
> directory was, inconsistent and not well laid out. Then more discussion on how it could be laid
> out in relation to where various subsystem were laid out (ie drivers doc directory like there was
> a drivers src directory and the like).
>
> Therefore I placed it following that pattern.
>
> So what I am hearing is that documentation for a subsystem should just continue to be dumped into
> one directory with everything else.
>
> Okay, if that is the goal, I am fine with, but things are pretty jumbled up in there. I will know
> where it is at least.
The current status quo is that everything is in one directory.
If someone wants to put more structure into Documentation/ that would be
fine with me, but edac.txt being the only file under
Documentation/drivers/ doesn't make sense and only makes it harder to
find this file.
> doug t
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2007-11-05 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 17:06 [2.6 patch] move edac.txt " Adrian Bunk
2007-11-05 17:17 ` Alan Cox
2007-11-05 18:52 ` [2.6 patch] move edac.txt DOCUMENTATION " Doug Thompson
2007-11-05 19:14 ` Adrian Bunk [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=20071105191400.GB3444@stusta.de \
--to=bunk@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=dougthompson@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=norsk5@yahoo.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®