From: "Måns Rullgård" <mru@mru.ath.cx>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Structural changes for Documentation directory
Date: Thu, 21 Oct 2004 00:44:48 +0200 [thread overview]
Message-ID: <yw1xhdopvwkf.fsf@mru.ath.cx> (raw)
In-Reply-To: <1098311012.4989.86.camel@desktop.cunninghams>
Nigel Cunningham <ncunningham@linuxmail.org> writes:
> Hi.
>
> On Thu, 2004-10-21 at 06:51, Jim Nelson wrote:
>> I propose changing the structure of the Documentation directory to
>> reflect the structure of the kernel sources itself.
>
> It seems that people know where to find the source code for whatever
> they're seeking documentation for. If I didn't work on the code, I
> wouldn't look for suspend-to-{disk|ram} under kernel/. I have to admit,
> it's always seemed strange to me, too, that net and sound aren't under
> drivers :>
drivers/net ?
--
Måns Rullgård
mru@mru.ath.cx
next prev parent reply other threads:[~2004-10-20 22:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 20:51 Jim Nelson
2004-10-20 22:23 ` Nigel Cunningham
2004-10-20 22:44 ` Måns Rullgård [this message]
2004-10-20 22:30 ` Andrew Morton
2004-10-20 22:51 ` Jim Nelson
2004-10-21 4:20 ` Dave Jones
2004-10-21 4:38 ` Jim Nelson
2004-10-21 5:00 ` Andrew Morton
2004-10-21 5:05 ` Dave Jones
2004-10-21 5:07 ` Andrew Morton
2004-10-21 9:43 ` Jim Nelson
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=yw1xhdopvwkf.fsf@mru.ath.cx \
--to=mru@mru.ath.cx \
--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
Powered by JetHome