From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: graphical cset stats
Date: Wed, 24 Apr 2002 04:18:45 +0000 (UTC) [thread overview]
Message-ID: <aa5bn5$28v$1@penguin.transmeta.com> (raw)
In-Reply-To: <200204232240.g3NMe9231822@work.bitmover.com> <20020423232520.GA10479@kroah.com> <20020423203211.7a6d7078.dang@fprintf.net>
In article <20020423203211.7a6d7078.dang@fprintf.net>,
Daniel Gryniewicz <dang@fprintf.net> wrote:
>
>But it is interesting how it's an exponential progression.
I think it's a bit dangerous, because it is so misleading. Both the "top
performers" are clearly integrators rather than big coders, and I
suspect a lot of my "cset-points" are actually from the early BK tree
creation where every single cset got attributed to me simply because
they got merged from the historic non-SCM patch info.
Certainly looking at the SCM statistics from the last 500 ChangeSets, 63
of them were attributed to me ("Hey, Linus does 12% of all kernel coding
himself! Studly, man!"), but if you actually look at the details of the
changesets, you'll notice that I'm a total loser, and I end up doing
little coding and most of my changesets are merges, cset excludes,
kernel version updates etc ("Hey, Linus is a complete moron!")..
So I personally get a bit nervous about pretty graphs - they _seem_ to
say so much, yet they clearly don't tell enough. Which can be a bit
dangerous if somebody takes them too seriously. They're just simple
enough that you think you get the RealTruth(tm).
Linus
next prev parent reply other threads:[~2002-04-24 4:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-23 22:40 graphical cset stats Larry McVoy
2002-04-23 23:25 ` Greg KH
2002-04-24 0:32 ` Daniel Gryniewicz
2002-04-24 4:18 ` Linus Torvalds [this message]
2002-04-29 3:32 ` Rusty Russell
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='aa5bn5$28v$1@penguin.transmeta.com' \
--to=torvalds@transmeta.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox