From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Luis Machado <luis.machado@arm.com>, Tom Tromey <tom@tromey.com>,
Tom de Vries <tdevries@suse.de>
Subject: Re: [pushed] [gdb/testsuite] Clean up before compilation in gdb.ada/call-no-debug.exp
Date: Thu, 22 Jun 2023 10:01:47 -0600 [thread overview]
Message-ID: <87pm5n1o5w.fsf@tromey.com> (raw)
In-Reply-To: <4c9724bf-a94e-71b1-b4e2-1097e4f4e0ad@suse.de> (Tom de Vries via Gdb-patches's message of "Wed, 21 Jun 2023 07:31:18 +0200")
Tom> OK, another try. This version handles the make -j 2 without problems.
Looks good to me. Thanks.
Reviewed-By: Tom Tromey <tom@tromey.com>
Tom
next prev parent reply other threads:[~2023-06-22 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 11:33 Tom de Vries
2023-06-16 18:38 ` Tom Tromey
2023-06-17 10:50 ` Tom de Vries
2023-06-17 20:14 ` Tom Tromey
2023-06-19 14:25 ` Luis Machado
2023-06-19 14:26 ` Luis Machado
2023-06-19 17:12 ` Tom de Vries
2023-06-19 17:22 ` Tom Tromey
2023-06-21 5:31 ` Tom de Vries
2023-06-21 7:40 ` Luis Machado
2023-06-22 16:01 ` Tom Tromey [this message]
2023-06-19 17:19 ` 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=87pm5n1o5w.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--cc=tdevries@suse.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).