Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Martin Galvan <martin.galvan@tallertechnologies.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PING][PATCH] Fix PR gdb/17720 (Function names appear without namespace/class prefixes in backtrace for optimized code)
Date: Wed, 13 May 2015 21:13:00 -0000	[thread overview]
Message-ID: <CAOKbPbbm6AGe8+PLRkp6yWaV7_8+Ni2KUx4WqnWnvW0R1uw-_Q@mail.gmail.com> (raw)
In-Reply-To: <CADPb22SPYAuoDkToJ=B7uaXMH++pB0TYQ6D=c95NSJMG0V_yKQ@mail.gmail.com>

On Wed, May 13, 2015 at 6:10 PM, Doug Evans <dje@google.com> wrote:
> On Wed, May 13, 2015 at 2:04 PM, Martin Galvan
> <martin.galvan@tallertechnologies.com> wrote:
>> On Wed, May 13, 2015 at 5:58 PM, Doug Evans <dje@google.com> wrote:
>>>
>>> Committed.
>>>
>>> I forgot the extra step of setting the author correctly, but it's just
>>> one line so I'm leaving it.
>>
>> Well, considering that it solves a quite important issue and it took
>> me a really long time to find it, fix it, and then get it commited,
>> it'd be nice of you if you could fix the author :)
>
> Done.
>
> Time to get yourself commit access.

Thanks a lot!

-- 

Martin Galvan

Software Engineer

Taller Technologies Argentina

San Lorenzo 47, 3rd Floor, Office 5

Córdoba, Argentina

Phone: 54 351 4217888 / +54 351 4218211


      reply	other threads:[~2015-05-13 21:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 15:25 Martin Galvan
2015-04-23 15:52 ` Doug Evans
2015-04-23 15:53   ` Martin Galvan
2015-05-11 19:48   ` Martin Galvan
2015-05-13 20:58   ` Doug Evans
2015-05-13 21:05     ` Martin Galvan
2015-05-13 21:10       ` Doug Evans
2015-05-13 21:13         ` Martin Galvan [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=CAOKbPbbm6AGe8+PLRkp6yWaV7_8+Ni2KUx4WqnWnvW0R1uw-_Q@mail.gmail.com \
    --to=martin.galvan@tallertechnologies.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    /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