git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] t5608: avoid say and use skip_all for consistency

From
Junio C Hamano <gitster@pobox.com>
Date
May 24, 2020, 16:16 UTC
Message-ID
<xmqqeer9qpe6.fsf@gitster.c.googlers.com>
In-Reply-To
<nycvar.QRO.7.76.6.2005221459190.56@tvgsbejvaqbjf.bet>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 31 quoted lines
> Hi Carlo,
>
>> Subject : Re: [PATCH] t5608: avoid say and use skip_all for consistency
>
> It might make quite a bit of sense to add a visual indicator to "say" to
> make it clear that it is not a verb, but a function name. Otherwise
> non-native speakers such as myself (and maybe even native speakers) will
> stumble over the grammar of this sentence when trying to parse it.
>
> These would work better for me:
>
> 	t5608: avoid `say` and use `skip_all` for consistency
>
> or
>
> 	t5608: avoid say() and use skip_all() for consistency
>
> On Thu, 21 May 2020, Carlo Marcelo Arenas Belón wrote:
>
>> Printing a message directly to stdout could affect TAP processing
>> and is not really needed, as there is a standard way to skip all
>> tests that could be used instead (including a message).
>>
>> While at it, update the message to better reflect the use of
>> booleans and get rid of the prerequisite.
>
> Makes sense. I would have added a sentence to say that _all_ three test
> cases were guarded by the very same prereq, so `skip_all` is just much
> faster and idempotent.
>
> Otherwise, the patch looks good to me.

Thanks, both. I see a v2 has already been posted, so hopefully that would be the final version.

Previous: Johannes SchindelinNext: Carlo Marcelo Arenas Belón
Message 3 of 4 in “t5608: avoid say and use skip_all for consistency”
  1. t5608: avoid say and use skip_all for consistencyCarlo Marcelo Arenas Belón, May 21, 2020
  2. Johannes SchindelinMay 22, 2020
  3. Junio C HamanoMay 24, 2020
  4. t5608: avoid say() and use "skip_all" instead for consistencyCarlo Marcelo Arenas Belón, May 22, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.