From: Kristoffer Ericson <kristoffer.ericson@gmail.com>
To: Wang Chen <wangchen@cn.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de, corbet@lwn.net
Subject: Re: Who wrote 2.6.28
Date: Thu, 8 Jan 2009 18:53:43 +0100 [thread overview]
Message-ID: <20090108185343.27602b9f.kristoffer.ericson@gmail.com> (raw)
In-Reply-To: <496224D7.2030109@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 2003 bytes --]
On Mon, 05 Jan 2009 23:18:47 +0800
Wang Chen <wangchen@cn.fujitsu.com> wrote:
> As Jonathon and Greg did, I also made a statistic about who wrote the Linux kernel.
> The following data is for 2.6.28 development. (http://www.remword.com/kps_result/)
>
> 1. The attachment graph "commit.png" shows the change of commit amount of patches and changed lines.
> It seems that 2.6.28 has less commits than 2.6.27 of both patch set and changed lines.
>
> 2. The attachment graph "who.png" shows the involved developers and employers in each version of kernel.
> It seems that 2.6.28 has more developers and companies involved than previous two versions, but
> less than that of 2.6.25. From a long vision, more and more developers and companies join to the
> development of Linux kernel, but the increase speed is not so fast.
How about adjusting for large/small letters? eg. Kristoffer Ericson == kristoffer ericson. Or Ill just learn to use the same always :)
>
> 3. About TOP30 employers who commit most to kernel, (http://remword.com/kps_result/2_6_28_emtop)
> Hobbyists is still the most group who contribute most to kernel development.
>
> 4. About longtail, (http://remword.com/kps_result/2_6_28_lt)
> There are 624 people who committed less than 2 patch sets, but their contribution is about 8%
> of total.
>
> 5. About Reviewed-by and Tested-by.
> More and more review and test efforts are regarded by people, Tested-by sign number(173)
> is highest in kernel development history.
>
> 6. Anyone who wants to check some person or company's contribution curve, please use
> http://remword.com/kps_result/evolvement.php
>
> BTW:
> To collect information about developers' employ relationship, I search on the Internet
> (not by asking themselves) and use gitdm-config which is created by Jonathon and Greg.
> Thanks Jonathon and Greg :)
>
> --
> WCN
>
>
>
--
Kristoffer Ericson <kristoffer.ericson@gmail.com>
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-08 17:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 15:18 Wang Chen
2009-01-08 17:53 ` Kristoffer Ericson [this message]
2009-01-09 9:07 ` Wang Chen
2009-02-02 18:16 ` Kristoffer Ericson
2009-01-09 14:09 ` Jaswinder Singh Rajput
2009-01-09 22:11 ` David Miller
2009-01-10 21:31 ` Theodore Tso
2009-01-10 22:00 ` Greg KH
2009-01-12 2:03 ` Wang Chen
2009-01-12 4:09 ` Greg KH
2009-01-12 5:04 ` Wang Chen
2009-01-12 15:54 ` Jonathan Corbet
2009-01-13 6:16 ` Wang Chen
2009-01-14 20:25 ` Jonathan Corbet
2009-01-12 17:49 ` Theodore Tso
2009-01-12 17:53 ` Jonathan Corbet
2009-01-13 8:12 ` Wang Chen
2009-01-11 18:30 ` Pavel Machek
2009-01-12 2:12 ` Wang Chen
2009-01-12 1:51 ` Wang Chen
2009-01-12 15:45 ` Stephen Hemminger
2009-01-13 8:14 ` Wang Chen
2009-01-12 1:49 ` Wang Chen
2009-01-13 16:57 ` Jaswinder Singh Rajput
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=20090108185343.27602b9f.kristoffer.ericson@gmail.com \
--to=kristoffer.ericson@gmail.com \
--cc=corbet@lwn.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=wangchen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome