From: Andrew Burgess <aburgess@redhat.com>
To: Bruno Larsen <blarsen@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: handle invalid .exp names passed in TESTS
Date: Sun, 02 Oct 2022 18:06:37 +0100 [thread overview]
Message-ID: <87mtaegnoi.fsf@redhat.com> (raw)
In-Reply-To: <87k05vepci.fsf@redhat.com>
Andrew Burgess <aburgess@redhat.com> writes:
> Bruno Larsen <blarsen@redhat.com> writes:
>
>> Hi Andrew,
>>
>> Once again, very well timed patch as I had just noticed this problem!
>> Other than a typo (response inlined), my only comment is that, since you
>> are already renaming check-single, what do you think about renaming to
>> check-single-thread or check-sequential?
>
> Except I'm not really renaming check-single. I'm adding a dependency to
> check-single, and replacing the recipe for check-single. But
> check-single itself continues to exist just as it did before.
>
> I'm not against renaming check-single to something else, but I think it
> should probably be done as a separate patch with its own justification.
>
>> My reasoning is that when first reading the message and diff, I thought
>> this rule would test a single test, which left me confused for a minute.
>
> I can see that.
>
>>
>> Either way, I like the patch, and encourage you to approve it!
>
> I'll give this a little longer to see if anyone else has any thoughts,
> then I'll merge it.
I've gone ahead and merged this patch.
Thanks,
Andrew
prev parent reply other threads:[~2022-10-02 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-10 16:43 Andrew Burgess
2022-09-12 7:51 ` Bruno Larsen
2022-09-22 9:21 ` Andrew Burgess
2022-10-02 17:06 ` Andrew Burgess [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=87mtaegnoi.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=blarsen@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).