From: Tom Tromey <tom@tromey.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, tom@tromey.com, palves@redhat.com,
sergiodj@redhat.com, yao.qi@arm.com
Subject: Re: GDB 8.1 branching 2017-12-04 update
Date: Mon, 04 Dec 2017 15:07:00 -0000 [thread overview]
Message-ID: <877eu25y7h.fsf@tromey.com> (raw)
In-Reply-To: <20171204145644.hjd3jisybmndqn7p@adacore.com> (Joel Brobecker's message of "Mon, 4 Dec 2017 15:56:44 +0100")
Joel> * [TomT] PR breakpoint/22511
Joel> Regression in "commands"
I sent a couple of notes about this to the list last week, and I'm
waiting for a reply before proceeding.
Tom
next prev parent reply other threads:[~2017-12-04 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 14:56 Joel Brobecker
2017-12-04 15:07 ` Tom Tromey [this message]
2017-12-04 15:21 ` Pedro Alves
2017-12-04 15:17 ` Pedro Alves
2017-12-04 17:02 ` Joel Brobecker
2017-12-09 0:17 ` Pedro Alves
2017-12-11 4:24 ` Joel Brobecker
2017-12-04 16:23 ` Yao Qi
2017-12-04 16:52 ` Joel Brobecker
2017-12-04 16:25 ` Pedro Alves
2017-12-04 17:11 ` Sergio Durigan Junior
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=877eu25y7h.fsf@tromey.com \
--to=tom@tromey.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=sergiodj@redhat.com \
--cc=yao.qi@arm.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).