From: Tom Tromey <tom@tromey.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: Tom Tromey <tom@tromey.com>,
Andrew Burgess <aburgess@redhat.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Guard against killing unrelated processes in amd64-disp-step.exp
Date: Mon, 07 Aug 2023 16:14:24 -0600 [thread overview]
Message-ID: <87v8dq7b5r.fsf@tromey.com> (raw)
In-Reply-To: <ydd350vhsf7.fsf@CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's message of "Mon, 07 Aug 2023 15:51:24 +0200")
>>>>> "Rainer" == Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
Rainer> Re-tested on amd64-pc-solaris2.11 and x86_64-pc-linux-gnu.
Rainer> Ok for master now?
Yes, thank you.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
prev parent reply other threads:[~2023-08-07 22:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 11:19 Rainer Orth
2023-07-13 16:34 ` Tom Tromey
2023-07-13 17:59 ` Rainer Orth
2023-07-14 17:25 ` Pedro Alves
2023-07-19 12:21 ` Rainer Orth
2023-07-15 13:38 ` Andrew Burgess
2023-07-19 12:37 ` Rainer Orth
2023-08-01 14:05 ` Rainer Orth
2023-08-02 20:56 ` Tom Tromey
2023-08-07 13:51 ` Rainer Orth
2023-08-07 22:14 ` 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=87v8dq7b5r.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).