From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <palves@redhat.com>
Subject: patch pings
Date: Fri, 11 Aug 2017 20:10:00 -0000 [thread overview]
Message-ID: <87y3qpvpad.fsf@pokyo> (raw)
Hi Pedro. Here is the patch ping I promised you.
Integer printing regression fix:
https://sourceware.org/ml/gdb-patches/2017-07/msg00460.html
"bt N" bug fix:
https://sourceware.org/ml/gdb-patches/2017-07/msg00200.html [latest note]
https://sourceware.org/ml/gdb-patches/2017-06/msg00746.html [your question]
https://sourceware.org/ml/gdb-patches/2017-04/msg00630.html [the patch]
There's another pending series (another set of backtrace changes) but it
seems I haven't yet addressed your review comments, so that's on me
still.
thanks,
Tom
next reply other threads:[~2017-08-11 20:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 20:10 Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-28 13:34 Patch pings Maciej W. Rozycki
2016-07-12 18:27 Patch Pings Tom Tromey
2016-07-12 18:49 ` Eli Zaretskii
2016-07-12 18:56 ` Eli Zaretskii
2016-07-13 16:29 ` Tom Tromey
2016-07-14 16:54 ` Tom Tromey
2016-06-24 20:52 patch pings 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=87y3qpvpad.fsf@pokyo \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).