From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/2] Make make-check-all.sh more accessible
Date: Tue, 7 Nov 2023 18:18:47 +0000 [thread overview]
Message-ID: <cover.1699381067.git.aburgess@redhat.com> (raw)
Love the make-check-all.sh script. This series aims to make the
script easier to use.
---
Andrew Burgess (2):
gdb/testsuite: log 'make check' command in make-check-all.sh
gdb/testsuite: add a new check-all-boards target
gdb/Makefile.in | 8 +++++++
gdb/testsuite/Makefile.in | 19 +++++++++++++++
gdb/testsuite/README | 42 +++++++++++++++++++++++++++++++++
gdb/testsuite/make-check-all.sh | 4 ++++
4 files changed, 73 insertions(+)
base-commit: 2029e13917d53d2289d3ebb390c4f40bd2112d21
--
2.25.4
next reply other threads:[~2023-11-07 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 18:18 Andrew Burgess [this message]
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 ` [PATCH 0/2] Make make-check-all.sh more accessible Tom Tromey
2023-11-28 10:46 ` 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=cover.1699381067.git.aburgess@redhat.com \
--to=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).