From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/2] Make make-check-all.sh more accessible
Date: Mon, 13 Nov 2023 10:29:45 -0700 [thread overview]
Message-ID: <87v8a5sgs6.fsf@tromey.com> (raw)
In-Reply-To: <cover.1699381067.git.aburgess@redhat.com> (Andrew Burgess's message of "Tue, 7 Nov 2023 18:18:47 +0000")
>>>>> "Andrew" == Andrew Burgess <aburgess@redhat.com> writes:
Andrew> Love the make-check-all.sh script. This series aims to make the
Andrew> script easier to use.
FWIW I looked at these & didn't see anything amiss. I have never used
this script so I don't know whether I ought to really be approving it.
Tom
next prev parent reply other threads:[~2023-11-13 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 18:18 Andrew Burgess
2023-11-07 18:18 ` [PATCH 1/2] gdb/testsuite: log 'make check' command in make-check-all.sh Andrew Burgess
2023-11-24 15:36 ` Tom de Vries
2023-11-07 18:18 ` [PATCH 2/2] gdb/testsuite: add a new check-all-boards target Andrew Burgess
2023-11-24 16:14 ` Tom de Vries
2023-11-13 17:29 ` Tom Tromey [this message]
2023-11-28 10:46 ` [PATCH 0/2] Make make-check-all.sh more accessible 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=87v8a5sgs6.fsf@tromey.com \
--to=tom@tromey.com \
--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).