public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Thompson <norsk5@yahoo.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, Adrian Bunk <bunk@kernel.org>
Cc: 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 10:52:01 -0800 (PST)	[thread overview]
Message-ID: <293742.55428.qm@web50101.mail.re2.yahoo.com> (raw)
In-Reply-To: <20071105171733.307a562a@the-village.bc.nu>

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.

doug t



--- Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> On Mon, 5 Nov 2007 18:06:08 +0100
> Adrian Bunk <bunk@kernel.org> wrote:
> 
> > There's no reason for edac.txt for being at this unusual place.
> > 
> > Signed-off-by: Adrian Bunk <bunk@kernel.org>
> 
> Acked-by: Alan Cox <alan@redhat.com>
> 
> 


W1DUG

  reply	other threads:[~2007-11-05 18:52 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 two levels up Adrian Bunk
2007-11-05 17:17 ` Alan Cox
2007-11-05 18:52   ` Doug Thompson [this message]
2007-11-05 19:14     ` [2.6 patch] move edac.txt DOCUMENTATION " Adrian Bunk

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=293742.55428.qm@web50101.mail.re2.yahoo.com \
    --to=norsk5@yahoo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bluesmoke-devel@lists.sourceforge.net \
    --cc=bunk@kernel.org \
    --cc=dougthompson@xmission.com \
    --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