From: Jiri Slaby <jirislaby@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: Xose Vazquez Perez <xose.vazquez@gmail.com>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Documentation dir is a mess
Date: Mon, 21 Nov 2005 17:46:35 +0100 [thread overview]
Message-ID: <4381F9EB.2070505@gmail.com> (raw)
In-Reply-To: <200511211028.28944.rob@landley.net>
Rob Landley napsal(a):
>On Sunday 20 November 2005 06:19, 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:
>>
>>Documentation/
>>Documentation/arch/
>>Documentation/arch/i386/
>>[...]
>>Documentation/drivers/
>>Documentation/drivers/net/
>>Documentation/drivers/scsi/
>>[...]
>>Documentation/net
>>[...]
>>
>>
>
>Perhaps you're looking for "make htmldocs"?
>
>
This is not, what he wants.
>Where would you put Documentation/unicode.txt in your proposed layout? Or
>
>
Documentation/others? or sth.
>Documentation/filesystems/proc.txt?
>
>
It is somewhere, why to move it, simply rename the directory to fs, as
he mentioned.
Sorting is not a problem in my opinion. If no other problem occurs, it
sounds good to me.
regards,
--
Jiri Slaby www.fi.muni.cz/~xslaby
\_.-^-._ jirislaby@gmail.com _.-^-._/
B67499670407CE62ACC8 22A032CC55C339D47A7E
next prev parent reply other threads:[~2005-11-21 16:46 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
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 [this message]
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=4381F9EB.2070505@gmail.com \
--to=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=rob@landley.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.