From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/mi: check thread exists when creating thread-specific b/p
Date: Mon, 03 Apr 2023 19:11:43 +0300 [thread overview]
Message-ID: <83lej9uerk.fsf@gnu.org> (raw)
In-Reply-To: <874jpxc69x.fsf@redhat.com> (message from Andrew Burgess via Gdb-patches on Mon, 03 Apr 2023 16:52:26 +0100)
> Date: Mon, 03 Apr 2023 16:52:26 +0100
> From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
>
>
> Ping!
Sorry for the delay. OK for the documentation parts.
Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2023-04-03 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 20:58 Andrew Burgess
2023-04-03 15:52 ` Andrew Burgess
2023-04-03 16:11 ` Eli Zaretskii [this message]
2023-04-28 23:18 ` Andrew Burgess
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=83lej9uerk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aburgess@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).