From: Chris Packham <judge.packham@gmail.com>
To: viresh kumar <viresh.linux@gmail.com>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [Query] Update email-id in kernel source
Date: Thu, 14 Jun 2012 21:44:34 +1200 [thread overview]
Message-ID: <4FD9B282.7090106@gmail.com> (raw)
In-Reply-To: <4FD860A9.4000804@gmail.com>
On 06/13/2012 09:43 PM, Chris Packham wrote:
> On 06/13/2012 09:24 PM, viresh kumar wrote:
>> Hi guys,
>>
>> I have recently changed my company and am required to update my email address in
>> kernel source.
>>
>> I can only see one way of doing that:
>> - Do a git grep, update all files, commit and post the patch.
>>
>> Is there any better way of doing this that git provides, by which even
>> 'git log' would show
>> the latest id available? I heard from a friend but don't know if it exists.
>>
>> --
>> Viresh
>> --
>> To unsubscribe from this list: send the line "unsubscribe git" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> Not sure if the kernel maintains one but projects can use a .mailmap[1]
> file to do just this kind of thing. You'd still have to update code if
> you want people to get hold of you from MODULE_AUTHOR statements.
>
> --
> [1] - http://www.git-scm.com/docs/git-shortlog
git log does support the .mailmap feature with the %aE format option but
it looks like it doesn't do it by default. I'm guessing performance is
probably the reason. Anyone else care to comment?
(Re-send. Sorry for the spam, I can't convince my phone not to send HTML)
prev parent reply other threads:[~2012-06-14 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 9:24 [Query] Update email-id in kernel source viresh kumar
2012-06-13 9:43 ` Chris Packham
2012-06-14 9:44 ` Chris Packham [this message]
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=4FD9B282.7090106@gmail.com \
--to=judge.packham@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=viresh.linux@gmail.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;
as well as URLs for NNTP newsgroup(s).