From: Tom Tromey <tom@tromey.com>
To: Magne Hov via Gdb-patches <gdb-patches@sourceware.org>
Cc: Magne Hov <mhov@undo.io>
Subject: Re: [PATCH v2 0/2] Improve handling of thread numbers for reverse execution targets
Date: Tue, 19 Sep 2023 10:34:40 -0600 [thread overview]
Message-ID: <87wmwm6s0v.fsf@tromey.com> (raw)
In-Reply-To: <20230707162451.3605544-1-mhov@undo.io> (Magne Hov via Gdb-patches's message of "Fri, 7 Jul 2023 17:24:49 +0100")
>>>>> "Magne" == Magne Hov via Gdb-patches <gdb-patches@sourceware.org> writes:
Magne> I've addressed two comments from Lancelot.
Magne> I'm not aware of any maintainers that are directly responsible for any of the
Magne> files I've touched, so I'm not sure who's best placed to approve these changes.
Thank you for the patches. I'm sorry about the delay on this, TBH I was
hoping someone else would get to it first.
I sent one comment about patch #1, but you don't need to resubmit the
series -- you can just fix that, rebuild, and check it in.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
prev parent reply other threads:[~2023-09-19 16:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 8:36 [PATCH " Magne Hov
2023-06-29 8:36 ` [PATCH 1/2] gdb: keep record " Magne Hov
2023-06-29 9:01 ` Lancelot SIX
2023-06-29 9:38 ` Magne Hov
2023-06-29 8:36 ` [PATCH 2/2] gdb: retain thread-specific breakpoints in " Magne Hov
2023-07-07 16:24 ` [PATCH v2 0/2] Improve handling of thread numbers for " Magne Hov
2023-07-07 16:24 ` [PATCH v2 1/2] gdb: keep record " Magne Hov
2023-07-13 12:21 ` Bruno Larsen
2023-09-19 16:33 ` Tom Tromey
2023-09-20 16:42 ` Pedro Alves
2023-09-20 17:00 ` Magne Hov
2023-09-20 17:13 ` Pedro Alves
2023-07-07 16:24 ` [PATCH v2 2/2] gdb: retain thread-specific breakpoints in " Magne Hov
2023-07-13 12:22 ` Bruno Larsen
2023-08-18 14:27 ` [PING][PATCH v2 0/2] Improve handling of thread numbers for " Magne Hov
2023-09-18 11:38 ` Magne Hov
2023-09-19 16:34 ` Tom Tromey [this message]
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=87wmwm6s0v.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=mhov@undo.io \
/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).