From: Theodore Tso <tytso@mit.edu>
To: Yang Hongyang <yanghy@cn.fujitsu.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-doc@vger.kernel.org, mtk.manpages@gmail.com,
rdunlap@xenotime.net
Subject: Re: Documentation:Update the INDEX of the documents
Date: Wed, 25 Feb 2009 09:59:50 -0500 [thread overview]
Message-ID: <20090225145950.GJ7064@mit.edu> (raw)
In-Reply-To: <49A4F06B.6030205@cn.fujitsu.com>
On Wed, Feb 25, 2009 at 03:16:59PM +0800, Yang Hongyang wrote:
> There are so many 00-INDEX file that are missing description of the
> current files in the dir. Such as 00-INDEX in
> Documentation/x86/,Documentation/networking/,Documentation/ and so
> on.
>
> It's a large amount of work for someone to go through all these
> documents and make summaries.
>
> I'm willing to do some of the work but if someone else pick these
> up(especially the authors of these new files) it will be a great
> help.^_^
Before you embark on this large amount of work, we should probably ask
a question first --- how useful are the 00-INDEX files? I don't find
them particularly interesting, given that my normal way of finding
documentation in the Documentation directory is:
find . -type f | xargs grep <keyword>
Or, if I have a git tree of the Linux sources handy:
git grep <keyword> -- Documentation
If folks do find the 00-INDEX files useful, my suggestion would be to
make a way of automatically extracting them from the individual files
and/or directories, and then making the 00-INDEX files to be
automatically generated.
- Ted
next prev parent reply other threads:[~2009-02-25 15:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 7:16 Documentation:Update the INDEX of the documents Yang Hongyang
2009-02-25 7:16 ` Yang Hongyang
2009-02-25 9:42 ` Rob Landley
2009-02-25 9:42 ` Rob Landley
2009-02-25 14:59 ` Theodore Tso [this message]
2009-02-25 15:05 ` Yang Hongyang
2009-02-25 15:05 ` Yang Hongyang
2009-02-25 15:25 ` Yang Hongyang
2009-02-25 15:25 ` Yang Hongyang
2009-02-25 15:56 ` Theodore Tso
2009-02-26 0:49 ` Yang Hongyang
2009-02-26 0:49 ` Yang Hongyang
2009-02-26 0:52 ` Randy Dunlap
2009-02-26 0:59 ` Yang Hongyang
2009-02-26 2:37 ` Theodore Tso
2009-02-26 6:04 ` Rob Landley
2009-02-25 19:30 ` Rob Landley
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=20090225145950.GJ7064@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=yanghy@cn.fujitsu.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.