From: Jeff Law <law@redhat.com>
To: Ian Lance Taylor <iant@google.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
Tom Tromey <tromey@redhat.com>, gdb <gdb@sourceware.org>,
Binutils <binutils@sourceware.org>
Subject: Re: git login -> name mapping
Date: Thu, 03 Oct 2013 19:49:00 -0000 [thread overview]
Message-ID: <524DCA61.7060109@redhat.com> (raw)
In-Reply-To: <CAKOQZ8zniopzKPcb4ixg+J2w3J50jGL3=gUk_Y2c1hiXrPq8Cw@mail.gmail.com>
On 10/03/13 13:48, Ian Lance Taylor wrote:
>>> 136:gmealer=FIXME <gmealer@cygnus>
>
> George Mealer? Really not sure.
Sounds correct to me. This thread is like a trip down memory lane...
jeff
next prev parent reply other threads:[~2013-10-03 19:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 17:25 Tom Tromey
2013-10-03 18:16 ` Tom Tromey
2013-10-03 18:44 ` Frank Ch. Eigler
2013-10-03 18:52 ` Tom Tromey
2013-10-03 19:45 ` Jonas Maebe
2013-10-03 20:49 ` Eric Christopher
2013-10-03 19:48 ` Ian Lance Taylor
2013-10-03 19:49 ` Jeff Law [this message]
2013-10-03 20:24 ` Tom Tromey
2013-10-04 1:20 ` Sergio Durigan Junior
2013-10-04 8:10 ` Alan Modra
2013-10-04 9:02 ` Catalin Marinas
2013-10-06 20:01 ` Maxim Kuvyrkov
2013-10-07 15:15 ` Frank Ch. Eigler
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=524DCA61.7060109@redhat.com \
--to=law@redhat.com \
--cc=binutils@sourceware.org \
--cc=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=iant@google.com \
--cc=tromey@redhat.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