From: Randy Dunlap <rdunlap@xenotime.net>
To: Rob Landley <rob@landley.net>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
paulus@samba.org
Subject: Re: [PATCH] Minor fix to Documentation/powerpc/00-INDEX
Date: Sat, 11 Aug 2007 14:33:34 -0700 [thread overview]
Message-ID: <20070811143334.60f90af4.rdunlap@xenotime.net> (raw)
In-Reply-To: <200708092342.35238.rob@landley.net>
On Thu, 9 Aug 2007 23:42:35 -0500 Rob Landley wrote:
> Signed-off-by: Rob Landley <rob@landley.net>
>
> I have a python script to convert 00-INDEX files into index.html files, and a
> second script to show 404 errors in the result as well as files/directories
> nothing links to. (It's not very useful yet, but in case you're wondering
> http://kernel.org/doc/docdiridx.py and http://kernel.org/doc/doclinkcheck.py
> .)
>
> Anyway, my simple index.html generator breaks on the Documentation/powerpc
> directory because one of the description lines is two lines long. This
> patch joins those two lines together into one line. This is the only
> instance (so far) of this problem.
If Paul wants to merge this, then OK, but I'm not aware of any rule
that the file descriptions inside INDEX files must be only one line
long... is that documented somewhere? (if so, where?)
Maybe the script should allow for this?
> ---
>
> In case you're wondering, here are the current the 404 errors in the
> various 00-INDEX files. Fixing all this is on my todo list:
>
> Documentation/ecryptfs.txt
> Documentation/time_interpolators.txt
> Documentation/arm/SA1100
> Documentation/arm/XScale
> Documentation/arm/empeg
> Documentation/arm/nwfpe
> Documentation/isdn/README.eicon
> Documentation/fb/clgenfb.txt
> Documentation/networking/ethertap.txt
> Documentation/filesystems/reiser4.txt
> Documentation/scsi/AM53C974.txt
> Documentation/scsi/ChangeLog
>
> The "files and directories not linked to" list is 679 lines long.
>
> diff -r /dev/null Documentation/powerpc/00-INDEX
> --- a/Documentation/powerpc/00-INDEX Thu Aug 09 08:40:21 2007 -0700
> +++ b/Documentation/powerpc/00-INDEX Thu Aug 09 20:49:03 2007 -0500
> @@ -6,8 +6,7 @@ 00-INDEX
> 00-INDEX
> - this file
> cpu_features.txt
> - - info on how we support a variety of CPUs with minimal compile-time
> - options.
> + - info on how we support a variety of CPUs with minimal compile-time options.
> eeh-pci-error-recovery.txt
> - info on PCI Bus EEH Error Recovery
> hvcs.txt
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-08-11 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 4:42 Rob Landley
2007-08-11 21:33 ` Randy Dunlap [this message]
2007-08-12 20:01 ` Rob Landley
2007-08-12 20:16 ` Jesper Juhl
2007-08-12 21:57 ` Randy Dunlap
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=20070811143334.60f90af4.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rob@landley.net \
/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
all inboxes | Powered by JetHome®