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

Re: [RFC/PATCH v2] t3300-*.sh: Fix a TAP parse error

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jul 24, 2012, 19:17 UTC
Message-ID
<20120724191707.GA5210@burratino>
In-Reply-To
<500EEDF4.7050007@ramsay1.demon.co.uk>
Hi,
Ramsay Jones wrote:
Show 5 quoted lines
> Hi Jonathan,
>
> This version of the patch only moves code to determine the test
> prerequisite to the outer level, while leaving the 'setup' aspects
> of the first test in place.

I guess I don't see the point. The current convention of "don't do anything complicated outside test assertions" is easy to explain. What new convention are you suggesting to replace it?

Thanks, Jonathan

Previous: Ramsay JonesNext: Ramsay Jones
Message 2 of 3 in “t3300-*.sh: Fix a TAP parse error”
  1. t3300-*.sh: Fix a TAP parse errorRamsay Jones, Jul 24, 2012
  2. Jonathan NiederJul 24, 2012
  3. Ramsay JonesJul 25, 2012

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.