public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
	linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] Add some missing Documentation/*/00-INDEX files
Date: Sun, 12 Aug 2007 14:54:15 -0500	[thread overview]
Message-ID: <200708121454.15856.rob@landley.net> (raw)
In-Reply-To: <46BF44A6.7010401@s5r6.in-berlin.de>

On Sunday 12 August 2007 12:34:30 pm Stefan Richter wrote:
> Jesper Juhl wrote:
> > On 12/08/07, Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
> >> Isn't it with 00-INDEX just like with the "Last Updated:" footers in
> >> documentation texts?
> >
> > That is certainly a risk, yes. But it shouldn't be hard to write a
> > small script to check if the 00-INDEX files are up-to-date, that will
> > make it pretty simple to update them once in a while if people forget.
>
> Or use the first line of each text file to describe what the file is about.

The first line of "unicode.txt" is:
                 Last update: 2005-01-17, version 1.4

The first line of "keys.txt" (and keys-request-key.txt) is:
                         ============================

The first line of sx.txt is blank, although that's easy enough to work around.

Lots of first lines redundantly have the filename in them, others have 
trailing information like the first nonblank line of kref.txt:

> krefs allow you to add reference counters to your objects.  If you

This heuristic seems to need about as much cleanup as just fixing 00-INDEX.txt 
in all the directories.

> And BTW, if authors insist on "Last Updated:", make it a header rather
> than a footer.  Increases the chance that submitters remember to update it.

Why not just use the source control system to review the actual revision 
history of the file?

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

  reply	other threads:[~2007-08-12 19:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-11 22:45 [PATCH 0/5] Add some missing Documentation/*/00-INDEX files Jesper Juhl
2007-08-11 22:46 ` [PATCH 1/5] Add a 00-INDEX file to Documentation/auxdisplay/ Jesper Juhl
2007-08-16  9:12   ` Miguel Ojeda
2007-08-11 22:47 ` [PATCH 2/5] Add a 00-INDEX file to Documentation/mips/ Jesper Juhl
2007-08-11 22:47 ` [PATCH 3/5] Add a 00-INDEX file to Documentation/sysctl/ Jesper Juhl
2007-08-11 22:48 ` [PATCH 4/5] Add a 00-INDEX file to Documentation/telephony/ Jesper Juhl
2007-08-11 22:49 ` [PATCH 5/5] Add a 00-INDEX file to Documentation/watchdog/ Jesper Juhl
2007-08-14 18:29   ` Wim Van Sebroeck
2007-08-12 12:48 ` [PATCH 0/5] Add some missing Documentation/*/00-INDEX files Stefan Richter
2007-08-12 17:10   ` Jesper Juhl
2007-08-12 17:34     ` Stefan Richter
2007-08-12 19:54       ` Rob Landley [this message]
2007-08-12 20:17         ` Stefan Richter
2007-08-12 21:11           ` Rob Landley
2007-08-12 21:47             ` Stefan Richter
2007-08-13  5:24               ` Rob Landley
2007-08-12 20:48     ` Rob Landley
2007-08-12 20:03   ` Rob Landley
2007-08-12 20:11     ` Jesper Juhl
2007-08-12 21:00       ` Rob Landley
2007-08-12 20:49 ` Rob Landley
2007-08-31 21:21 ` [PATCH 2/5][resend] Add a 00-INDEX file to Documentation/mips/ Jesper Juhl
2007-08-31 21:21 ` [PATCH 3/5][resend] Add a 00-INDEX file to Documentation/sysctl/ Jesper Juhl
2007-08-31 21:21 ` [PATCH 4/5][resend] Add a 00-INDEX file to Documentation/telephony/ Jesper Juhl

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=200708121454.15856.rob@landley.net \
    --to=rob@landley.net \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=stefanr@s5r6.in-berlin.de \
    /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