public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wang Chen <wangchen@cn.fujitsu.com>
To: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de, corbet@lwn.net
Subject: Re: Who wrote 2.6.28
Date: Mon, 12 Jan 2009 09:49:05 +0800	[thread overview]
Message-ID: <496AA191.5060703@cn.fujitsu.com> (raw)
In-Reply-To: <3f9a31f40901090609n29b4e36dwe6fff7fdfc705c7e@mail.gmail.com>

Jaswinder Singh Rajput said the following on 2009-1-9 22:09:
> On Mon, Jan 5, 2009 at 8:48 PM, 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.
>>
> 
> In http://remword.com/kps_result/2_6_29_whole_line.html
> Earlier I was using email address: Jaswinder Singh
> <jaswinder@infradead.org> (Unknown #25) and now I am using:
> Jaswinder Singh Rajput <jaswinderrajput@gmail.com> (Unknown #25)
> 
> If possible can you link above two emails.
> 

Sure. Will fix.
Thanks Jaswinder.

  parent reply	other threads:[~2009-01-12  1:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 15:18 Who wrote 2.6.28 Wang Chen
2009-01-08 17:53 ` Kristoffer Ericson
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 [this message]
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=496AA191.5060703@cn.fujitsu.com \
    --to=wangchen@cn.fujitsu.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@suse.de \
    --cc=jaswinderlinux@gmail.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