This is the mail archive of the
mailing list for the GCC project.
Re: Handling the dje ambiguity
- From: Ian Lance Taylor <iant at google dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: "Eric S. Raymond" <esr at thyrsus dot com>, GCC Development <gcc at gcc dot gnu dot org>
- Date: Thu, 27 Aug 2015 18:25:07 -0700
- Subject: Re: Handling the dje ambiguity
- Authentication-results: sourceware.org; auth=none
- References: <20150827225303 dot GA19560 at thyrsus dot com> <alpine dot DEB dot 2 dot 10 dot 1508272255350 dot 20506 at digraph dot polyomino dot org dot uk>
On Thu, Aug 27, 2015 at 3:58 PM, Joseph Myers <firstname.lastname@example.org> wrote:
> On Thu, 27 Aug 2015, Eric S. Raymond wrote:
>> For the curios, here's what it looks like to deal with this in reposurgeon:
>> authors read <gcc.map
>> # Deal with the one ambiguous username.
>> (<1>..<14639> & /master/b) | /premerge-fsf-branch/b assign gcc2
>> <gcc2> authors read <<EOF
>> dje = Doug Evans <email@example.com>
> Bearing in mind that that email address is wrong (I don't know what's
> preferred, gcc.map currently has firstname.lastname@example.org for him as
> devans; MAINTAINERS says email@example.com)...
Yes, Doug Evans is firstname.lastname@example.org, or, I suppose, email@example.com.
And he is the same person as devans in current GCC changes, if he's