From: Carlos O'Donell <carlos@redhat.com>
To: DJ Delorie <dj@redhat.com>
Cc: Szabolcs.Nagy@arm.com, libc-alpha@sourceware.org, nd@arm.com
Subject: Re: [v2, with help] Re: run one test
Date: Mon, 30 Sep 2019 20:51:00 -0000 [thread overview]
Message-ID: <c1ddd97e-ea9e-fe6a-27d8-f730b7f8d26e@redhat.com> (raw)
In-Reply-To: <xnpnjhk13d.fsf@greed.delorie.com>
On 9/30/19 3:58 PM, DJ Delorie wrote:
> "Carlos O'Donell" <carlos@redhat.com> writes:
>> Bikeshed. Suggest "onecheck" alias given that 'make test' is the same
>> as 'make check.'
>
> Can add. I was thinking we already have "make nss/tests" and "make
> tests", we call them "tests" and "testsuite", and "make check" is just a
> convenience target:
>
> # Support the GNU standard name for this target.
> .PHONY: check
> check: tests
>
> Or we could call it "make test" (note singular) but I suspect this would
> be confusing, and "make check" (note singular!) vs "make checks".
In summary:
make check = make tests
make onecheck = make test
Or is the tests vs test too confusing?
--
Cheers,
Carlos.
next prev parent reply other threads:[~2019-09-30 20:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 20:41 DJ Delorie
2019-09-25 21:12 ` Carlos O'Donell
2019-09-25 21:18 ` DJ Delorie
2019-09-26 9:10 ` Szabolcs Nagy
2019-09-30 19:37 ` [v2, with help] " DJ Delorie
2019-09-30 19:47 ` Carlos O'Donell
2019-09-30 19:58 ` DJ Delorie
2019-09-30 20:51 ` Carlos O'Donell [this message]
2019-09-30 20:07 ` [v3, " DJ Delorie
2019-09-30 20:57 ` Carlos O'Donell
2019-10-02 18:44 ` [v4, " DJ Delorie
2019-10-18 19:06 ` Carlos O'Donell
2019-10-18 19:47 ` DJ Delorie
2019-09-30 20:12 ` [v2, " Andreas Schwab
2019-09-30 20:20 ` DJ Delorie
2019-09-30 20:26 ` Andreas Schwab
2019-10-04 12:36 ` Florian Weimer
2019-10-04 17:33 ` DJ Delorie
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=c1ddd97e-ea9e-fe6a-27d8-f730b7f8d26e@redhat.com \
--to=carlos@redhat.com \
--cc=Szabolcs.Nagy@arm.com \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
/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).