From: Junio C Hamano <gitster@pobox.com>
To: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH v2 2/2] t6300: check for cat-file exit status code
Date: Thu, 19 Aug 2021 13:19:42 -0700 [thread overview]
Message-ID: <xmqqim01yyox.fsf@gitster.g> (raw)
In-Reply-To: <68ee769121195eb61bb51fd6a27d22a8dddb13b6.1629263759.git.congdanhqx@gmail.com> ("Đoàn Trần Công Danh"'s message of "Wed, 18 Aug 2021 12:19:27 +0700")
Đoàn Trần Công Danh <congdanhqx@gmail.com> writes:
> In test_atom(), we're piping the output of cat-file to tail(1),
> thus, losing its exit status.
>
> Let's use a temporary file to preserve git exit status code.
>
> Signed-off-by: Đoàn Trần Công Danh <congdanhqx@gmail.com>
> ---
> t/t6300-for-each-ref.sh | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/t/t6300-for-each-ref.sh b/t/t6300-for-each-ref.sh
> index 93126341b3..cc0f5b6627 100755
> --- a/t/t6300-for-each-ref.sh
> +++ b/t/t6300-for-each-ref.sh
> @@ -66,7 +66,9 @@ test_atom() {
> case $type in
> tag)
> # We cannot use $3 as it expects sanitize_pgp to run
> - expect=$(git cat-file tag $ref | tail -n +6 | wc -c) ;;
> + git cat-file tag $ref >out &&
> + expect=$(tail -n +6 <out | wc -c) &&
It is not wrong per-se, but do we need a redirect '<' here? "tail"
takes filename(s) on the command line, but is there a reason to feed
the contents from the standard input?
> + rm -f out ;;
> tree | blob)
> expect="" ;;
> commit)
next prev parent reply other threads:[~2021-08-19 20:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 11:48 [PATCH] t6300: don't run cat-file on non-existent object Đoàn Trần Công Danh
2021-08-17 21:44 ` Johannes Schindelin
2021-08-18 5:19 ` [PATCH v2 0/2] t6300: clear warning when running without gpg Đoàn Trần Công Danh
2021-08-18 5:19 ` [PATCH v2 1/2] t6300: don't run cat-file on non-existent object Đoàn Trần Công Danh
2021-08-19 20:16 ` Junio C Hamano
2021-08-18 5:19 ` [PATCH v2 2/2] t6300: check for cat-file exit status code Đoàn Trần Công Danh
2021-08-19 20:19 ` Junio C Hamano [this message]
2021-08-18 10:33 ` [PATCH v2 0/2] t6300: clear warning when running without gpg Johannes Schindelin
2021-08-21 1:36 ` [PATCH v3 " Đoàn Trần Công Danh
2021-08-21 1:36 ` [PATCH v3 1/2] t6300: don't run cat-file on non-existent object Đoàn Trần Công Danh
2021-08-21 1:36 ` [PATCH v3 2/2] t6300: check for cat-file exit status code Đoàn Trần Công Danh
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=xmqqim01yyox.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.