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

Greg KH said the following on 2009-1-11 6:00:
> On Sat, Jan 10, 2009 at 04:31:21PM -0500, Theodore Tso wrote:
>> On Fri, Jan 09, 2009 at 02:11:24PM -0800, David Miller wrote:
>>> From: "Jaswinder Singh Rajput" <jaswinderlinux@gmail.com>
>>> Date: Fri, 9 Jan 2009 19:39:17 +0530
>>>
>>>> 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.
>>> This reminds me that I noticed another one that needs linking,
>>> shemminger@linux-foundation.org became shemminger@vyatta.com
>> ... and most of the engineers listed as working for the Linux
>> Foundation in the above-mentioned analysis don't....
> 

Thanks Ted and Greg.

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?

If you mean the page "2_6_29_whole.html".
Here are only four people be listed:
Stephen Hemminger <shemminger@vyatta.com> \\working for vyatta now?
Theodore Ts'o <tytso@mit.edu>
Linus Torvalds <torvalds@linux-foundation.org>
Chris Wright <chrisw@osdl.org> \\redhat engineer

I will fix that.

> If you look at the tool that Jon wrote, and the data files that I keep
> up to date, this is already handled there.
> 
> thanks,
> 

Greg, I've used your gitdm-config-2.6. And don't see any update, where should
I find your latest work?


  reply	other threads:[~2009-01-12  2:03 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 [this message]
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=496AA506.20900@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