public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Randy Dunlap <rdunlap@xenotime.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: Sun, 12 Aug 2007 15:01:01 -0500	[thread overview]
Message-ID: <200708121501.01358.rob@landley.net> (raw)
In-Reply-To: <20070811143334.60f90af4.rdunlap@xenotime.net>

On Saturday 11 August 2007 4:33:34 pm Randy Dunlap wrote:
> 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?)

Documentation/00-INDEX line 5:

> Please try and keep the descriptions small enough to fit on one line.

There was only one instance of it not being the case.  I can use indentation 
level instead (which is what Kconfig uses to identify help text, so I'm not 
leaking pythonisms into the kernel that aren't already there), but the one 
line thing seemed to be an existing standard.

I'm also relying on the first file in the list being documentation for 
00-INDEX itself.  (If it breaks, I'll either try to derive a new heuristic 
and change the script, or submit a patch to change the index.  That one would 
be a more difficult heuristic to replace, though.)

> Maybe the script should allow for this?

*shrug*  I can go either way on that, but people get all funny about 
whitespace being significant and the one line thing wasn't my idea. :)

Rob
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

  reply	other threads:[~2007-08-12 20:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-10  4:42 [PATCH] Minor fix to Documentation/powerpc/00-INDEX Rob Landley
2007-08-11 21:33 ` Randy Dunlap
2007-08-12 20:01   ` Rob Landley [this message]
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=200708121501.01358.rob@landley.net \
    --to=rob@landley.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=rdunlap@xenotime.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