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

Re: [PATCH] t: fix whitespace around &&

From
Andrei Rybak <rybak.a.v@gmail.com>
Date
Mar 15, 2020, 18:35 UTC
Message-ID
<0ad0600c-d1fc-0f44-dae1-7bd0fc22b3e8@gmail.com>
In-Reply-To
<CAPig+cTGqEdr+rjRCfKmcm=ab3vKnUokd6KyrsoBiy=AO9nnOQ@mail.gmail.com>
On 2020-03-15 19:20, Eric Sunshine wrote:
Show 15 quoted lines
> On Sun, Mar 15, 2020 at 2:09 PM Andrei Rybak <rybak.a.v@gmail.com> wrote:
>> Add missing spaces before '&&' and switch tabs to spaces.  Also fix the
>> space after redirection operator in t3701-add-interactive.sh while we're
>> here.  These issues were found using `git grep '[^ ]&&$'`.
>>
>> Signed-off-by: Andrei Rybak <rybak.a.v@gmail.com>
>> ---
>> diff --git a/t/t9500-gitweb-standalone-no-errors.sh b/t/t9500-gitweb-standalone-no-errors.sh
>> @@ -348,7 +348,7 @@ test_expect_success \
>> -        echo "To be changed and have mode changed" > 07-change-mode-change     &&
>> +        echo "To be changed and have mode changed" > 07-change-mode-change &&
> 
> The commit message talks about dropping whitespace after the '>'
> redirection operator (and some of the changes in this patch do so),
> however, this change neglects that cleanup.

Good catch. t9500-gitweb-standalone-no-errors.sh has 35 of these vs 19 redirects with correct formatting, so it might be better to fix those redirects in a separate patch. What do you think?

Show 6 quoted lines
>> @@ -361,7 +361,7 @@ test_expect_success \
>> -        echo "Changed and have mode changed" > 07-change-mode-change   &&
>> +        echo "Changed and have mode changed" > 07-change-mode-change &&
> 
> Ditto.
> 
Thanks for review.
Previous: Eric SunshineNext: Eric Sunshine
Message 3 of 7 in “t: fix whitespace around &&”
  1. t: fix whitespace around &&Andrei Rybak, Mar 15, 2020
  2. Eric SunshineMar 15, 2020
  3. Andrei RybakMar 15, 2020
  4. Eric SunshineMar 15, 2020
  5. 1/2 t9500: remove spaces after redirect operatorsAndrei Rybak, Mar 22, 2020
  6. 2/2 t: fix whitespace around &&Andrei Rybak, Mar 22, 2020
  7. Junio C HamanoMar 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.