All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul G. Allen" <pgallen@randomlogic.com>
To: "kplug-list@kernel-panic.org" <kplug-list@kernel-panic.org>
Cc: "Linux kernel developer's mailing list" 
	<linux-kernel@vger.kernel.org>,
	"kplug-lpsg@kernel-panic.org" <kplug-lpsg@kernel-panic.org>
Subject: Re: Linx Kernel Source tree and metrics
Date: Fri, 27 Jul 2001 13:40:58 -0700	[thread overview]
Message-ID: <3B61D1DA.49AFC88D@randomlogic.com> (raw)
In-Reply-To: <3B612D26.BA131CEC@randomlogic.com> <01072714523106.00285@starship> <200107271308.f6RD8EA02743@mobilix.ras.ucalgary.ca>


> 
> Daniel Phillips writes:

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?



Richard Gooch wrote:

> 
> Hm. Interesting. But I note it has the devfsd source code in there as
> well. That's definately not part of the kernel!
> 
>                                 Regards,
> 
>                                         Richard....
> Permanent: rgooch@atnf.csiro.au
> Current:   rgooch@ras.ucalgary.ca
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


Answer to Daniel:

The program I used is a purchased product. So, no, it won't be GPL. I have no control over the contents of the reports other than addin/removing source
files/trees that are parsed and hand editing the generated HTML. Since there's over 1GB of HTML, the editing part is definetely out. :D


Answer to Richard:

I simply parsed the entire /usr/src/linux-2.4.2 tree (including the modules) and applicable gcc header files. I may have missed a few, I may have gotten a few
too many. Those that are more "in the know" than I can feed me info so I can correct the files/trees that are parsed.

PGA

-- 
Paul G. Allen
UNIX Admin II/Programmer
Akamai Technologies, Inc.
www.akamai.com
Work: (858)909-3630
Cell: (858)395-5043

  reply	other threads:[~2001-07-27 20:33 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
2001-07-27 13:08   ` Richard Gooch
2001-07-27 20:40     ` Paul G. Allen [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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=3B61D1DA.49AFC88D@randomlogic.com \
    --to=pgallen@randomlogic.com \
    --cc=kplug-list@kernel-panic.org \
    --cc=kplug-lpsg@kernel-panic.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.