Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sterling Augustine <saugustine@google.com>
To: Eric Christopher <echristo@gmail.com>
Cc: Simon Marchi <simon.marchi@polymtl.ca>,
	gdb-patches <gdb-patches@sourceware.org>
Subject: Re: Recent commit in binutils-gdb
Date: Wed, 29 Apr 2020 21:10:53 -0700	[thread overview]
Message-ID: <CAEG7qUyr-Gx=v3_8KU=3pUkCT2+gi0-SBLCGh4PKbzdHyNwnxQ@mail.gmail.com> (raw)
In-Reply-To: <CALehDX4qCdg0AgNi_cHoJpjmGcXn78cdFQNkwPj2i15ErsQOGQ@mail.gmail.com>

The commit was proposed here:

https://sourceware.org/pipermail/gdb/2020-March/000012.html

And approved here:

https://sourceware.org/pipermail/gdb/2020-April/048466.html

On Wed, Apr 29, 2020 at 6:57 PM Eric Christopher <echristo@gmail.com> wrote:

> Hi Simon!
>
> Sterling misplaced his commit keys and asked me to commit on his behalf.
> IIRC it was approved a couple months ago and just now had the chance to
> commit.
>
> I tried to set the author etc correctly but let me know if I
> missed anything.
>
> -eric
>
> On Wed, Apr 29, 2020, 5:50 PM Simon Marchi <simon.marchi@polymtl.ca>
> wrote:
>
>> Hi Eric,
>>
>> I was just wondering about the recent commit 84ed7a4725 in the
>> binutils-gdb
>> git repo, touching dwarf2/read.c, there's no commit message and I haven't
>> seen
>> it pass by on the mailing list.  Where does this come from, what is it
>> about?
>>
>> Simon
>>
>


  reply	other threads:[~2020-04-30  4:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30  0:50 Simon Marchi
2020-04-30  1:57 ` Eric Christopher
2020-04-30  4:10   ` Sterling Augustine [this message]
2020-04-30  5:49     ` Tom de Vries
2020-04-30 13:24       ` Andrew Burgess
2020-04-30 17:01         ` Tom de Vries
2020-04-30 19:24           ` Eric Christopher
2020-04-30 16:17     ` Simon Marchi

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='CAEG7qUyr-Gx=v3_8KU=3pUkCT2+gi0-SBLCGh4PKbzdHyNwnxQ@mail.gmail.com' \
    --to=saugustine@google.com \
    --cc=echristo@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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