From: Junio C Hamano <gitster@pobox.com>
To: Ghanshyam Thakkar <shyamthakkar001@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] t0024: refactor to have single command per line
Date: Thu, 18 Jan 2024 15:18:02 -0800 [thread overview]
Message-ID: <xmqqfryunsd1.fsf@gitster.g> (raw)
In-Reply-To: <20240118215407.8609-2-shyamthakkar001@gmail.com> (Ghanshyam Thakkar's message of "Fri, 19 Jan 2024 03:23:40 +0530")
Ghanshyam Thakkar <shyamthakkar001@gmail.com> writes:
> Refactor t0024 to avoid having multiple chaining commands on a single
> line, according to current styling norms.
>
> e.g turn
> ( mkdir testdir && cd testdir && echo "in testdir" )
> into:
> mkdir testdir &&
> (
> cd testdir &&
> echo "in testdir"
> )
>
> This is also described in the Documentation/CodingGuidelines file.
Sure.
Subject: t0024: style fix
t0024 has multiple command invocations on a single line,
which goes against the style given by CodingGuidelines.
would be sufficient.
> - ( mkdir untarred && cd untarred && "$TAR" -xf ../test.tar ) &&
> + mkdir untarred &&
> + (
> + cd untarred &&
> + "$TAR" -xf ../test.tar
> + ) &&
I think we assume "$TAR" is modern enough to know about the "C"
option (see t/t5004-archive-corner-cases.sh), so
mkdir untarred &&
"$TAR" Cxf untarred test.tar
without even a subshell may be sufficient.
> @@ -30,7 +34,11 @@ test_expect_success UNZIP 'zip archive' '
>
> git archive --format=zip HEAD >test.zip &&
>
> - ( mkdir unzipped && cd unzipped && "$GIT_UNZIP" ../test.zip ) &&
> + mkdir unzipped &&
> + (
> + cd unzipped &&
> + "$GIT_UNZIP" ../test.zip
> + ) &&
I do not think we assume "$GIT_UNZIP" to always know about the
equivalent of "C" (is that "-d exdir"?), so what you wrote is the
best we can do.
Thanks.
next prev parent reply other threads:[~2024-01-18 23:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 21:53 [PATCH 1/2] t0024: avoid losing exit status to pipes Ghanshyam Thakkar
2024-01-18 21:53 ` [PATCH 2/2] t0024: refactor to have single command per line Ghanshyam Thakkar
2024-01-18 23:18 ` Junio C Hamano [this message]
2024-01-19 0:57 ` Ghanshyam Thakkar
2024-01-19 3:40 ` Ghanshyam Thakkar
2024-01-18 23:04 ` [PATCH 1/2] t0024: avoid losing exit status to pipes Junio C Hamano
2024-01-19 1:36 ` [PATCH v2 " Ghanshyam Thakkar
2024-01-19 1:36 ` [PATCH v2 2/2] t0024: style fix Ghanshyam Thakkar
2024-01-19 3:33 ` [PATCH v3 1/2] t0024: avoid losing exit status to pipes Ghanshyam Thakkar
2024-01-19 3:33 ` [PATCH v3 2/2] t0024: style fix Ghanshyam Thakkar
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=xmqqfryunsd1.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=shyamthakkar001@gmail.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 NNTP newsgroup(s).