public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wang Chen <wangchen@cn.fujitsu.com>
To: Theodore Tso <tytso@mit.edu>, Wang Chen <wangchen@cn.fujitsu.com>,
	Greg KH <gregkh@suse.de>, David Miller <davem@davemloft.net>,
	jaswinderlinux@gmail.com, linux-kernel@vger.kernel.org,
	corbet@lwn.net
Subject: Re: Who wrote 2.6.28
Date: Tue, 13 Jan 2009 16:12:35 +0800	[thread overview]
Message-ID: <496C4CF3.1030404@cn.fujitsu.com> (raw)
In-Reply-To: <20090112174927.GG21793@mit.edu>

Theodore Tso said the following on 2009-1-13 1:49:
> On Mon, Jan 12, 2009 at 10:03:50AM +0800, Wang Chen wrote:
>> Ted, when you said this, do you mean the page "all_whole.html"?
>> If so, my explanation is that this page lists all the people who
>> ever worked for TLF since 2.6.13 age.
>> Is there any mistake?
> 
> I can't remember for certain which one I was looking at; it might have
> been 2._6_26_whole_line.html or 2.6.27's whole_line.html:
> 
> # No.1 Stephen Hemminger <shemminger@linux-foundation.org> 42263
> # No.2 Linus Torvalds <torvalds@linux-foundation.org> 1165
> # No.3 Theodore Ts'o <tytso@mit.edu> 42
> # No.4 Chris Wright <chrisw@osdl.org> 35
> # No.5 Christoph Lameter <cl@linux-foundation.org> 14
> 
> Of the above technically only Linus Torvalds is an _employee_ of the
> Linux Foundation.  I'm technically an employee of IBM, but I'm on loan
> to the Linux Foundation.
> 

Thanks Ted.
I will update my database.

> One of the things which get confusing is that people's employers
> change over time, so if you are mapping engineers to company, it's not
> enough to use just an e-mail address and map it to a company name;
> ideally you need to take an e-mail address and/or name and date range,
> and then map that to a compay name.  For example Alan Cox was
> previously at Red Hat, but he will be changing employers to Intel as
> of some date in January, 2009, but he will be keeping his e-mail
> address.
> 

Yes. This is in my todo list.

  parent reply	other threads:[~2009-01-13  8:12 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 [this message]
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=496C4CF3.1030404@cn.fujitsu.com \
    --to=wangchen@cn.fujitsu.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=gregkh@suse.de \
    --cc=jaswinderlinux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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