From: Junio C Hamano <gitster@pobox.com>
To: Ghanshyam Thakkar <shyamthakkar001@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] t0024: avoid losing exit status to pipes
Date: Thu, 18 Jan 2024 15:04:25 -0800 [thread overview]
Message-ID: <xmqqmst2nszq.fsf@gitster.g> (raw)
In-Reply-To: <20240118215407.8609-1-shyamthakkar001@gmail.com> (Ghanshyam Thakkar's message of "Fri, 19 Jan 2024 03:23:39 +0530")
Ghanshyam Thakkar <shyamthakkar001@gmail.com> writes:
> Replace pipe with redirection operator '>' to store the output
> to a temporary file after 'git archive' command since the pipe
> will swallow the command's exit code and a crash won't
> necessarily be noticed.
OK. I think this case what the patch does is the right thing. If
we were creating a huge tar archive and have the downstream only
consuming for a small disk footprint (e.g., "git archive | tar tf -"),
use of pipe (and loss of exit status) may be justified, but I do not
think that is the case here.
> Also refactor an existing use of '>' to avoid having a space after
> '>', according to Documentation/CodingGuidelines.
It may be just me, but I wouldn't call that "refactor", which we
often use to refer to changing the way an existing functional unit
works internally, by splitting the innard of a function into
separate helper functions, by replacing the open-coded duplicate
with calls to such helper functions, etc. Correcting the coding
style violation is merely a "fix".
Also fix an unwanted space after '>' redirection to match
the style in CodingGuidelines.
In any case, the patch text looks good.
Thanks.
> Signed-off-by: Ghanshyam Thakkar <shyamthakkar001@gmail.com>
> ---
> t/t0024-crlf-archive.sh | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/t/t0024-crlf-archive.sh b/t/t0024-crlf-archive.sh
> index a34de56420..fa4da7c2b3 100755
> --- a/t/t0024-crlf-archive.sh
> +++ b/t/t0024-crlf-archive.sh
> @@ -9,7 +9,7 @@ test_expect_success setup '
>
> git config core.autocrlf true &&
>
> - printf "CRLF line ending\r\nAnd another\r\n" > sample &&
> + printf "CRLF line ending\r\nAnd another\r\n" >sample &&
> git add sample &&
>
> test_tick &&
> @@ -19,8 +19,8 @@ test_expect_success setup '
>
> test_expect_success 'tar archive' '
>
> - git archive --format=tar HEAD |
> - ( mkdir untarred && cd untarred && "$TAR" -xf - ) &&
> + git archive --format=tar HEAD >test.tar &&
> + ( mkdir untarred && cd untarred && "$TAR" -xf ../test.tar ) &&
>
> test_cmp sample untarred/sample
next prev parent reply other threads:[~2024-01-18 23:04 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
2024-01-19 0:57 ` Ghanshyam Thakkar
2024-01-19 3:40 ` Ghanshyam Thakkar
2024-01-18 23:04 ` Junio C Hamano [this message]
2024-01-19 1:36 ` [PATCH v2 1/2] t0024: avoid losing exit status to pipes 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=xmqqmst2nszq.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).