From: Jonathan Corbet <corbet@lwn.net>
To: Theodore Tso <tytso@mit.edu>
Cc: Wang Chen <wangchen@cn.fujitsu.com>, Greg KH <gregkh@suse.de>,
David Miller <davem@davemloft.net>,
jaswinderlinux@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: Who wrote 2.6.28
Date: Mon, 12 Jan 2009 10:53:48 -0700 [thread overview]
Message-ID: <20090112105348.127debb4@bike.lwn.net> (raw)
In-Reply-To: <20090112174927.GG21793@mit.edu>
On Mon, 12 Jan 2009 12:49:27 -0500
Theodore Tso <tytso@mit.edu> wrote:
> 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.
FWIW, the gitdm code handles that just fine. Of course, it does
require keeping the database current, which is always a challenge.
jon
next prev parent reply other threads:[~2009-01-12 17:54 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
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 [this message]
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=20090112105348.127debb4@bike.lwn.net \
--to=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 \
--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
all inboxes | Powered by JetHome®