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 16:11:02 -0500 [thread overview]
Message-ID: <200708121611.02971.rob@landley.net> (raw)
In-Reply-To: <46BF6AE2.9070105@s5r6.in-berlin.de>
On Sunday 12 August 2007 3:17:38 pm Stefan Richter wrote:
> > 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.
That's just extra markup for me to filter out. Either the first line nonblank
has a special meaning or it doesn't. Currently, it doesn't.
> 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?
You're too optimistic, but if it's something we can check automatically we can
find and fix instances that don't. (Although in this case "automatic" means
we generate the index, put it on the web, and either we notice mistakes or
people point them out to us.)
> - 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.
You are aware that some of the files in Documentation aren't text, right?
There's example code in C, there's docbook, there's a gif and an xpm...
What variant of "fast" do you mean? Processing the entire directory takes a
fraction of a second on my laptop.
I'm not really invested in 00-INDEX, but I point out that it currently exists
and I've indicated a willingness to do work to update it. If you want to do
your own work to update something else, be my guest. I'll be over here.
> There could also be "From: " and/or "Cc: " headers for authorship and
> maintainership metadata.
You're adding complexity again. Why are you adding complexity?
> (Of course maintainership metadata could also
> go into extra files like 00-INDEX or MAINTAINERS.
00-INDEX is a bad place for it, and MAINTAINERS hasn't go the granularity.
> Authorship metadata
> of more recent documentation files is actually available in the source
> control system.)
I was wondering if this would be noticed...
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
next prev parent reply other threads:[~2007-08-12 21:11 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
2007-08-12 20:17 ` Stefan Richter
2007-08-12 21:11 ` Rob Landley [this message]
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=200708121611.02971.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