From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tom@tromey.com>,
Christian Biesinger via gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Add an objfile getter to gdb.Type
Date: Tue, 04 Jun 2019 22:07:00 -0000 [thread overview]
Message-ID: <CAPTJ0XHpmVFPY4shy=pbG2QorSnVsXe_DrwwMYK88Fmo3WwW2w@mail.gmail.com> (raw)
In-Reply-To: <a6f6388c-3d0e-55cc-be02-9345c36237d8@redhat.com>
On Tue, Jun 4, 2019 at 4:48 PM Pedro Alves <palves@redhat.com> wrote:
>
> On 6/4/19 4:47 PM, Tom Tromey wrote:
> >>>>>> "Christian" == Christian Biesinger via gdb-patches <gdb-patches@sourceware.org> writes:
> >
> > Christian> I don't think I'll be writing enough patches for that to be worth it,
> > Christian> so it would be great if you could commit this. Thanks!
> >
> > I checked it in.
>
> FYI, I pushed in these fixes to the ChangeLog files.
>
> Christian, the issue here is that entry paths are relative to the
> corresponding ChangeLog file.
Oh, sorry about that! Thanks for fixing!
Christian
next prev parent reply other threads:[~2019-06-04 22:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 18:40 Christian Biesinger via gdb-patches
2019-05-23 19:01 ` Eli Zaretskii
2019-05-23 19:34 ` Simon Marchi
2019-05-23 20:36 ` Christian Biesinger via gdb-patches
2019-05-23 20:32 ` Christian Biesinger via gdb-patches
2019-05-23 21:06 ` Simon Marchi
2019-05-23 21:25 ` Christian Biesinger via gdb-patches
2019-05-23 21:37 ` Christian Biesinger via gdb-patches
2019-05-28 22:07 ` Tom Tromey
2019-05-30 17:01 ` Christian Biesinger via gdb-patches
2019-06-03 19:50 ` Tom Tromey
2019-06-03 20:28 ` Christian Biesinger via gdb-patches
2019-06-04 15:47 ` Tom Tromey
2019-06-04 21:48 ` Pedro Alves
2019-06-04 22:07 ` Christian Biesinger via gdb-patches [this message]
2019-06-05 1:51 ` Tom Tromey
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='CAPTJ0XHpmVFPY4shy=pbG2QorSnVsXe_DrwwMYK88Fmo3WwW2w@mail.gmail.com' \
--to=gdb-patches@sourceware.org \
--cc=cbiesinger@google.com \
--cc=palves@redhat.com \
--cc=tom@tromey.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