[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070804035206.GB23330@suse.de>
Date: Fri, 3 Aug 2007 20:52:06 -0700
From: Greg KH <gregkh@...e.de>
To: Rob Landley <rob@...dley.net>
Cc: Randy Dunlap <rdunlap@...otime.net>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Theodore Tso <tytso@....edu>, leoli@...escale.com,
Gerrit Huizenga <gh@...ibm.com>,
"H. Peter Anvin" <hpa@...or.com>,
"Kunai, Takashi" <kunai@...ux-foundation.jp>,
holzheu@...ux.vnet.ibm.com,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
lf_kernel_messages@...ux-foundation.org, mtk-manpages@....net,
jack@...e.cz, pavel@....cz, tim.bird@...sony.com,
arjan@...radead.org, sam@...nborg.org, jengelh@...putergmbh.de,
joe@...ches.com, auke-jan.h.kok@...el.com, hansendc@...ibm.com,
davem@...emloft.net, Valdis.Kletnieks@...edu, kenistoj@...ibm.com,
schwidefsky@...ibm.com, heiko.carstens@...ibm.com,
linux-doc@...r.kernel.org
Subject: Re: Documentation of kernel messages (Summary)
On Fri, Aug 03, 2007 at 03:32:04PM -0400, Rob Landley wrote:
>
> These days I'm trying to create an html index that links into Documentation in
> a coherent order (with categories and everything), and using automated tools
> to detect files that aren't linked to, or links that point to a file that
> isn't there anymore. This is obviously still a work in progress, but I think
> it's a better approach.
Better than cleaning up what we have in the kernel source tree? Why not
work on that first, then the "automated" type stuff would be much easier
to do later, right?
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists