From: Greg KH <greg@kroah.com>
To: Philipp Riemer <ruderphilipp@gmail.com>
Cc: "Josh Boyer" <jwboyer@gmail.com>, "Joe Perches" <joe@perches.com>,
"Paul Mundt" <lethal@linux-sh.org>, "Michael Büsch" <m@bues.ch>,
"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
"Jiri Kosina" <jkosina@suse.cz>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
"Wang Chen" <ellre923@gmail.com>,
"Jonathan Corbet" <corbet@lwn.net>
Subject: Re: [GIT PULL] new mailmap file for the linux kernel git repository
Date: Wed, 16 May 2012 10:58:36 -0700 [thread overview]
Message-ID: <20120516175836.GB3094@kroah.com> (raw)
In-Reply-To: <CAFU-uVueBEOzC065jynvLqFU3S76yVqFB20B0q75sbRVSFsSgw@mail.gmail.com>
On Wed, May 16, 2012 at 07:01:54PM +0200, Philipp Riemer wrote:
> I thought about the fact that over time people move companies. In my
> case, I try to do some kind of time series analysis and thus it might
> be interesting to see who was employed but now works as a freelancer
> etc. Here, the opinion of other people who analyze the kernel such as
> Wang Chen, Greg KH, or Jonathan Corbet might be interesting...
The mailmap file does not show this type of thing very well at all, and
I wouldn't recommend trying to keep it up to date this way. I say this
as someone who tries to keep track of who is working for whom. This
information changes over time, and as others have pointed out, some
people use multiple email addresses to categorize their submittions
(work vs. hobby) for legal and personal reasons.
Our database has been made public at times, so you should be using that
instead of trying to update the mailmap file.
So while it might be nice to update it, why do you want to do so? We
have updated and cleaned-up log files publicly if you want to use those
for research (they are in my github archive). Modifying things here
probably would not be a good idea.
sorry,
greg k-h
next prev parent reply other threads:[~2012-05-16 17:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 14:25 Philipp Riemer
2012-05-16 14:38 ` Greg KH
2012-05-16 14:41 ` Jiri Kosina
2012-05-16 15:01 ` Philipp Riemer
2012-05-16 15:08 ` Greg KH
2012-05-16 15:21 ` Philipp Riemer
2012-05-31 16:08 ` Philipp Riemer
2012-05-31 19:25 ` Joe Perches
2012-05-31 20:15 ` Al Viro
2012-06-01 8:41 ` Philipp Riemer
2012-06-01 11:41 ` Alan Cox
2012-06-01 16:45 ` Al Viro
2012-06-01 15:16 ` Philipp Riemer
2012-06-28 5:21 ` Joe Perches
2012-06-28 9:00 ` Philipp Riemer
[not found] ` <CAD6jFUQAUAqSz3vAmQtvPFBQZC82DJ4dD9TdRs37DHTZjNUuOQ@mail.gmail.com>
[not found] ` <CAFU-uVs2i8Sf7CqUvndyo8-TUNH4CYjXzu4KXPhLvLo-JLcuWQ@mail.gmail.com>
2012-08-10 13:39 ` [PATCH] " Philipp Riemer
2012-06-01 7:58 ` [GIT PULL] " Greg KH
2012-06-01 16:22 ` Philipp Riemer
2012-06-01 16:23 ` Philipp Riemer
2012-05-16 16:10 ` Joe Perches
2012-05-16 16:46 ` Philipp Riemer
2012-05-16 16:49 ` Josh Boyer
2012-05-16 17:01 ` Philipp Riemer
2012-05-16 17:58 ` Greg KH [this message]
2012-05-16 16:52 ` Joe Perches
2012-06-04 6:28 ` Geert Uytterhoeven
2012-06-04 8:42 ` Philipp Riemer
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=20120516175836.GB3094@kroah.com \
--to=greg@kroah.com \
--cc=corbet@lwn.net \
--cc=ellre923@gmail.com \
--cc=jkosina@suse.cz \
--cc=joe@perches.com \
--cc=jwboyer@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m@bues.ch \
--cc=ruderphilipp@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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