From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] More uses of require
Date: Fri, 10 Mar 2023 07:56:55 -0700 [thread overview]
Message-ID: <875yb8mz7s.fsf@tromey.com> (raw)
In-Reply-To: <20230224-submit-require-fixes-v1-0-7cbcbbf613c9@tromey.com> (Tom Tromey's message of "Fri, 24 Feb 2023 13:28:27 -0700")
>>>>> Tom Tromey <tom@tromey.com> writes:
> I found some more places that can use 'require'. Before this series,
> some spots used "untested", some used "verbose", and some silently
> returned. I think it's better for the tests to try to be consistent
> in this sort of thing.
I've rebased this and once "make check" is done, I'm going to check it in.
Tom
prev parent reply other threads:[~2023-03-10 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 20:28 Tom Tromey
2023-02-24 20:28 ` [PATCH 1/4] Use require with target_info Tom Tromey
2023-02-24 20:28 ` [PATCH 2/4] Use require with gdb_skip_stdio_test Tom Tromey
2023-02-24 20:28 ` [PATCH 3/4] More uses of require with istarget Tom Tromey
2023-02-24 20:28 ` [PATCH 4/4] Use require with test_compiler_info Tom Tromey
2023-03-10 14:56 ` 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=875yb8mz7s.fsf@tromey.com \
--to=tom@tromey.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).