From: Tom Tromey <tom@tromey.com>
To: Simon Farre via Gdb-patches <gdb-patches@sourceware.org>
Cc: Simon Farre <simon.farre.cx@gmail.com>
Subject: Re: [PATCH v6] gdb/Python: Added ThreadExitedEvent
Date: Mon, 05 Jun 2023 09:55:35 -0600 [thread overview]
Message-ID: <87r0qpsy2w.fsf@tromey.com> (raw)
In-Reply-To: <20230605145254.100777-1-simon.farre.cx@gmail.com> (Simon Farre via Gdb-patches's message of "Mon, 5 Jun 2023 16:52:54 +0200")
>>>>> "Simon" == Simon Farre via Gdb-patches <gdb-patches@sourceware.org> writes:
Simon> v6:
Simon> Fix comments.
Simon> Fix copyright
Simon> Remove unnecessary test suite stuff. save_var had to stay, as it mutates
Simon> some test suite state that otherwise fails.
Thank you. This is ok.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
next prev parent reply other threads:[~2023-06-05 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 14:52 Simon Farre
2023-06-05 15:55 ` Tom Tromey [this message]
2023-06-24 1:27 ` Simon Marchi
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=87r0qpsy2w.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.farre.cx@gmail.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).