From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Rob Landley <rob@landley.net>
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 22:17:38 +0200 [thread overview]
Message-ID: <46BF6AE2.9070105@s5r6.in-berlin.de> (raw)
In-Reply-To: <200708121454.15856.rob@landley.net>
Rob Landley wrote:
> On Sunday 12 August 2007 12:34:30 pm Stefan Richter wrote:
>> Or use the first line of each text file to describe what the file is about.
...
> This heuristic seems to need about as much cleanup as just fixing 00-INDEX.txt
> in all the directories.
I didn't think of heuristics but rather of a style guideline. Maybe
prepend this metadata line with "Subject: " or so to distinguish it from
data.
What's the difference to 00-INDEX? It's inline. Hence,
- as soon as a majority of files have that header, authors of new
files will start to provide that header automatically. Or am I too
optimistic?
- it's a little bit faster to create these headers than to add them
to 00-INDEX: Just move the existing title to the top.
There could also be "From: " and/or "Cc: " headers for authorship and
maintainership metadata. (Of course maintainership metadata could also
go into extra files like 00-INDEX or MAINTAINERS. Authorship metadata
of more recent documentation files is actually available in the source
control system.)
>> 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?
Just to clarify: I'm *not* one of those who want the date in there.
--
Stefan Richter
-=====-=-=== =--- -==--
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-08-12 20:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 22:45 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
2007-08-12 20:17 ` Stefan Richter [this message]
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=46BF6AE2.9070105@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=jesper.juhl@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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®