From: Daniel Phillips <phillips@bonn-fries.net>
To: "Paul G. Allen" <pgallen@randomlogic.com>,
"Linux kernel developer's mailing list"
<linux-kernel@vger.kernel.org>,
"kplug-list@kernel-panic.org" <kplug-list@kernel-panic.org>,
"kplug-lpsg@kernel-panic.org" <kplug-lpsg@kernel-panic.org>
Subject: Re: Linx Kernel Source tree and metrics
Date: Fri, 27 Jul 2001 14:52:30 +0200 [thread overview]
Message-ID: <01072714523106.00285@starship> (raw)
In-Reply-To: <3B612D26.BA131CEC@randomlogic.com>
In-Reply-To: <3B612D26.BA131CEC@randomlogic.com>
On Friday 27 July 2001 10:58, Paul G. Allen wrote:
> For those interested, I have run the kernel (2.4.2-2) through a
> program and generated extensive HTML reports including call trees,
> function and data declarations, source code, and metrics. I plan to
> upgrade this to the latest kernel and keep it up to date (as much as
> possible :), but I am a) working with a kernel that I know currently
> runs on my dual Athlon, and b) wanted to test this out and run it by
> the two lists first.
>
> My bandwisth is currently limited (cable modem), but if it's decided
> that I'll keep this available, I will upload it to a web server with
> a couple T1's avalable (or maybe I will use one of our companies
> servers on a DS3 or greater).
>
> The URL is:
>
> http://24.5.14.144:3000/linux-kernel
>
> If you have any connection problems (and there may be, since it's
> currently running on the same machine I'm using to develop with - the
> dual Athlon), suggestions (even if it's "hey, dork, it's already
> available at http://xxx.yyy"), or whatever, please let me know.
Nit 1: I'd prefer the following format for the data dictionary:
-m (Local Object)[xref]
- [wavelan_cs.c, 564]
-
+m [xref] [wavelan_cs.c, 564] (Local Object)
I.e., three times as many entries on the screen and with the
constant-width part aligned.
Nit 2: You can drop the "Report" from the name of every section, we
know it's a report.
I'm continuing to explore this wonderful resource. Do you intend to
GPL the source?
--
Daniel
next prev parent reply other threads:[~2001-07-27 12:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-27 8:58 Linx Kernel Source tree and metrics Paul G. Allen
2001-07-27 12:52 ` Daniel Phillips [this message]
2001-07-27 13:08 ` Richard Gooch
2001-07-27 20:40 ` Paul G. Allen
2001-07-27 23:32 ` Paul G. Allen
[not found] <200107270917.f6R9HUt19989@antimatter.net>
2001-07-27 9:25 ` Paul G. Allen
2001-07-27 9:33 ` Paul G. Allen
2001-07-27 9:53 ` Paul G. Allen
2001-07-27 9:52 Thomas Foerster
2001-07-27 10:26 ` Paul G. Allen
2001-07-27 10:30 ` Neil Brown
2001-07-27 11:18 ` Jan-Benedict Glaw
2001-07-27 11:47 ` Paul G. Allen
[not found] <no.id>
2001-07-27 23:46 ` Alan Cox
2001-07-28 0:20 ` Paul G. Allen
2001-07-28 1:33 ` Paul G. Allen
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=01072714523106.00285@starship \
--to=phillips@bonn-fries.net \
--cc=kplug-list@kernel-panic.org \
--cc=kplug-lpsg@kernel-panic.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgallen@randomlogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).