From: Andrew Morton <akpm@osdl.org>
To: Hans Ulrich Niedermann <linux-kernel@n-dimensional.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fixing 2.6.0's broken documentation references
Date: Sat, 27 Dec 2003 16:08:34 -0800 [thread overview]
Message-ID: <20031227160834.2de6401d.akpm@osdl.org> (raw)
In-Reply-To: <864qvmjtez.fsf@n-dimensional.de>
Hans Ulrich Niedermann <linux-kernel@n-dimensional.de> wrote:
>
> Hi,
>
> I've noted that 2.6.0 contains broken references to documentation.
>
> I got sufficiently annoyed chasing doc files in the wrong place
> that I wrote a script to check the references to documentation
> files.
>
> Some documentation files have moved (e.g. Documentation/modules.txt
> to Documentation/kbuild/modules.txt). I adapted the references with a
> script. Patch attached.
Thanks.
> I couldn't find a maintainer for the documentation, the -doc lists are
> dead, so I ask here whether such patches stand a chance to be included
> into the main kernel tree.
>
> If yes, I'd like to do some more work as described below.
>
> 1. How to consistently reference to doc files?
>
> a) "linux/Documentation/"
> Still used in some places, but seems to be obsolete, as the top
> directory is now called "linux-${VERSION}".
>
> b) "../../Documentation/foo/bar.txt"
> There are also places where relative pathes are used. This takes
> extra space and "Documentation/" should be well-known anyway.
>
> c) "Documentation/"
> Most commonly used. Probably the way to go.
Yes, c).
> 2. Some files have been removed (examples: Configure.help, smp.tex).
> Fixing this requires manual rewrite of
> a) code comments
> b) kbuild help
> c) Documentation files
We can live with that. If someone cares enough, they'll fix it.
> 3. Now that I have written a script to scan the source tree, I could
> also start checking for broken references to http:// and ftp://
> URLs if desirable.
That wouldn't hurt.
next prev parent reply other threads:[~2003-12-28 0:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-27 13:12 Hans Ulrich Niedermann
2003-12-28 0:08 ` Andrew Morton [this message]
2003-12-28 3:34 ` Thomas Molina
2003-12-28 10:48 ` Michael Still
2003-12-28 22:02 ` Randy.Dunlap
2004-01-08 18:36 ` Hans Ulrich Niedermann
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=20031227160834.2de6401d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@n-dimensional.de \
--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