public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Gdb Patches <gdb-patches@sourceware.org>
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Patch Pings
Date: Tue, 12 Jul 2016 18:27:00 -0000	[thread overview]
Message-ID: <87vb0aogo9.fsf@tromey.com> (raw)

Hi.  I have a few unreviewed patches.  Ping.


Eli, CCing you for this patch, which needs a doc review:

https://sourceware.org/ml/gdb-patches/2016-06/msg00395.html


Previous ping was here:

https://sourceware.org/ml/gdb-patches/2016-06/msg00407.html


The unreviewed patches are:

[RFA 0/4] Add "pending" attribute to gdb.Breakpoint
https://sourceware.org/ml/gdb-patches/2016-05/msg00343.html

[RFA] PR python/15620, PR python/18620 - breakpoint events in Python
https://sourceware.org/ml/gdb-patches/2016-05/msg00368.html

[RFA] PR python/13598 - add before_prompt event
https://sourceware.org/ml/gdb-patches/2016-05/msg00370.html

[RFA] Fix PR cli/18053
https://sourceware.org/ml/gdb-patches/2016-06/msg00125.html

[RFA] PR python/20190 - compute TLS symbol without a frame
https://sourceware.org/ml/gdb-patches/2016-06/msg00070.html
This one had some comments, see the ensuing thread.


This one also is awaiting a response:

https://sourceware.org/ml/gdb-patches/2016-06/msg00395.html

thanks,
Tom

             reply	other threads:[~2016-07-12 18:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-12 18:27 Tom Tromey [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2017-08-11 20:10 patch pings Tom Tromey
2016-10-28 13:34 Patch pings Maciej W. Rozycki
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=87vb0aogo9.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=eliz@gnu.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).