From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>,
Christian Biesinger via gdb-patches <gdb-patches@sourceware.org>
Cc: Christian Biesinger <cbiesinger@google.com>
Subject: Re: [PATCH] Add an objfile getter to gdb.Type
Date: Tue, 04 Jun 2019 21:48:00 -0000 [thread overview]
Message-ID: <a6f6388c-3d0e-55cc-be02-9345c36237d8@redhat.com> (raw)
In-Reply-To: <87d0jtl5dm.fsf@tromey.com>
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.
From d3238f7d90715dad7e8da2a8c2486d26124b0c84 Mon Sep 17 00:00:00 2001
From: Pedro Alves <palves@redhat.com>
Date: Tue, 4 Jun 2019 22:44:36 +0100
Subject: [PATCH] Fix paths to ChangeLog files
---
gdb/ChangeLog | 4 ++--
gdb/doc/ChangeLog | 2 +-
gdb/testsuite/ChangeLog | 3 +--
3 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 933f23249ff..e36eae9ac16 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,8 +1,8 @@
2019-06-04 Christian Biesinger <cbiesinger@google.com>
Add objfile property to gdb.Type.
- * gdb/NEWS: Mention Python API addition.
- * gdb/python/py-type.c (typy_get_objfile): New method.
+ * NEWS: Mention Python API addition.
+ * python/py-type.c (typy_get_objfile): New method.
2019-06-03 Philippe Waroquiers <philippe.waroquiers@skynet.be>
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index ea98096845a..5da25996b1c 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,6 +1,6 @@
2019-06-04 Christian Biesinger <cbiesinger@google.com>
- * gdb/doc/python.texi: Document new gdb.Type.objfile property.
+ * python.texi: Document new gdb.Type.objfile property.
2019-06-03 Philippe Waroquiers <philippe.waroquiers@skynet.be>
diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index af451fa4e12..722249f822c 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,7 +1,6 @@
2019-06-04 Christian Biesinger <cbiesinger@google.com>
- * gdb/testsuite/gdb.python/py-type.exp: Test for new
- gdb.Type.objfile property.
+ * gdb.python/py-type.exp: Test for new gdb.Type.objfile property.
2019-06-03 Philippe Waroquiers <philippe.waroquiers@skynet.be>
--
2.14.5
next prev parent reply other threads:[~2019-06-04 21:48 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 [this message]
2019-06-04 22:07 ` Christian Biesinger via gdb-patches
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=a6f6388c-3d0e-55cc-be02-9345c36237d8@redhat.com \
--to=palves@redhat.com \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--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