From: Tom Tromey <tom@tromey.com>
To: Aaron Merey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Aaron Merey <amerey@redhat.com>
Subject: Re: [PING*2][PATCH] gdb/linespec.c: Fix missing source file during breakpoint re-set
Date: Mon, 09 Jan 2023 12:27:53 -0700 [thread overview]
Message-ID: <87y1qb8q4m.fsf@tromey.com> (raw)
In-Reply-To: <20230106235607.498218-1-amerey@redhat.com> (Aaron Merey via Gdb-patches's message of "Fri, 6 Jan 2023 18:56:07 -0500")
>>>>> "Aaron" == Aaron Merey via Gdb-patches <gdb-patches@sourceware.org> writes:
Aaron> Ping. I tweaked the testcase so that it applies to the master branch.
Oops, I reviewed the wrong version.
This one is ok. Thank you.
Tom
next prev parent reply other threads:[~2023-01-09 19:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 23:44 [PATCH] " Aaron Merey
2022-10-10 16:06 ` Bruno Larsen
2022-10-12 20:49 ` Aaron Merey
2022-10-13 7:59 ` Bruno Larsen
2022-10-14 0:47 ` Aaron Merey
2022-10-21 17:07 ` Aaron Merey
2023-01-06 23:56 ` [PING*2][PATCH] " Aaron Merey
2023-01-09 19:27 ` Tom Tromey [this message]
2023-01-10 1:15 ` Aaron Merey
2023-02-01 17:37 ` Andrew Burgess
2023-01-09 19:27 ` [PATCH] " 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=87y1qb8q4m.fsf@tromey.com \
--to=tom@tromey.com \
--cc=amerey@redhat.com \
--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).