From: Rob Landley <rob@landley.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] Documentation/make/headers_install.txt
Date: Mon, 6 Aug 2007 11:36:02 -0400 [thread overview]
Message-ID: <200708061036.02604.rob@landley.net> (raw)
In-Reply-To: <20070804200525.GA21961@uranus.ravnborg.org>
On Saturday 04 August 2007 3:05:25 pm Sam Ravnborg wrote:
> On Sat, Aug 04, 2007 at 02:07:18PM -0400, Rob Landley wrote:
> > From: Rob Landley <rob@landley.net>
> >
> > Signed-off-by: Rob Landley <rob@landley.net>
> >
> > Some documentation for "make headers_install".
> >
> > ---
> >
> > Earlier discussion was at http://lkml.org/lkml/2007/6/22/7 and I
> > believe I've responded to all of David's comments.
> >
> > --- /dev/null 2007-04-23 10:59:00.000000000 -0500
> > +++ linux-2.6/Documentation/make/headers_install.txt 2007-08-04
> > 13:04:51.000000000 -0500
>
> Any specific reason not to include this in Documentation/kbuild?
> I would prefer to have all kernel build stuff in one directory and
> we have Documentation/kbuild now.
That directory contains internal implementation details of the kernel
makefiles, and is not about how to use them if you don't plan to modify them.
This document is about how people can use one of the commands listed in "make
help", and is not about modifying the make files. It's a different category
of documentation. (Ideally, kbuild would go under make.)
That said, I don't really care where it goes, so if you prefer kbuild I can
drop it there. The organization of Documentation/ is fairly irrelevant to me
at this point.
Like most documentation, this file needs to be linked to from more than one
place: it needs to be brought to the attention of people building their own
linux-from-scratch style systems (the "what's in a linux root filesystem"
section of the index I'm building), it should be linked from a "building the
kernel" page (what kinds of output can the build produce), there should be
a "make help" page with hotlinks to the individual commands (like this and
menuconfig) that have more extensive documentation, etc.
Trying to do that in Documentation would be a pain. (Lots of symlinks with no
explanatory text? Lots of files called "index.txt" in each directory
reinventing Gopher, pointing you at a directory other than the one you're in
and hoping nothing ever moves?)
> Sam
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
prev parent reply other threads:[~2007-08-06 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 18:07 [PATCH] Documentation/make/headers_install.txt Rob Landley
2007-08-04 18:52 ` Jesper Juhl
2007-08-04 20:05 ` Sam Ravnborg
2007-08-06 15:36 ` Rob Landley [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=200708061036.02604.rob@landley.net \
--to=rob@landley.net \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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