From: Junio C Hamano <gitster@pobox.com>
To: Trieu Huynh <vikingtc4@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [GSoC PATCH 00/16] Microproject: avoid suppressing git's exit code
Date: Sat, 28 Mar 2026 17:44:48 -0700 [thread overview]
Message-ID: <xmqqpl4nh3b3.fsf@gitster.g> (raw)
In-Reply-To: <20260328200255.247759-1-vikingtc4@gmail.com> (Trieu Huynh's message of "Sun, 29 Mar 2026 05:02:39 +0900")
Trieu Huynh <vikingtc4@gmail.com> writes:
> Piping git command output directly to subsequent command (eg. grep)
> hides the exit code of git behind the pipe. A crash in git would go
> unnoticed because the shell only sees grep's exit code.
>
> This series extends the same fix to 16 more test files, following the
> approach introduced in t8003 [1] (redirect output to a temporary file,
> then use test_grep on that file).
>
> Note: t2206 is a special case -- some tests cd into a subdirectory
> that is itself a git repo and run 'git add .' on the whole working
> tree. To prevent the temporary file from being accidentally staged,
> it is written as '../actual', outside the inner repo.
>
> Related-to: https://lore.kernel.org/git/20260328132955.172262-1-vikingtc4@gmail.com/T/#t
> See-also: https://lore.kernel.org/git/xmqq4im2sjnu.fsf@gitster.g/T/#t
See also https://git.github.io/General-Microproject-Information/#:~:text=Only%20ONE%20quality%20focused%20microproject%20per%20applicant
Thanks.
next prev parent reply other threads:[~2026-03-29 0:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 20:02 [GSoC PATCH 00/16] Microproject: avoid suppressing git's exit code Trieu Huynh
2026-03-28 20:02 ` [GSoC PATCH 01/16] t7004: " Trieu Huynh
2026-03-28 20:02 ` [GSoC PATCH 02/16] t6423: " Trieu Huynh
2026-03-28 20:02 ` [GSoC PATCH 03/16] t6411: " Trieu Huynh
2026-03-28 20:02 ` [GSoC PATCH 04/16] t6101: " Trieu Huynh
2026-03-28 20:02 ` [GSoC PATCH 05/16] t6006: " Trieu Huynh
2026-03-28 20:02 ` [GSoC PATCH 06/16] t5304: " Trieu Huynh
2026-03-28 20:02 ` [GSoC PATCH 07/16] t4153: " Trieu Huynh
2026-03-29 15:59 ` Tian Yuchen
2026-03-28 20:02 ` [GSoC PATCH 08/16] t4150: " Trieu Huynh
2026-03-28 20:02 ` [GSoC PATCH 09/16] t4140: " Trieu Huynh
2026-03-28 20:02 ` [GSoC PATCH 10/16] t4039: " Trieu Huynh
2026-03-28 20:02 ` [GSoC PATCH 11/16] t3903: " Trieu Huynh
2026-03-29 16:14 ` Tian Yuchen
2026-03-28 20:02 ` [GSoC PATCH 12/16] t3701: " Trieu Huynh
2026-03-28 20:02 ` [GSoC PATCH 13/16] t3412: " Trieu Huynh
2026-03-28 20:02 ` [GSoC PATCH 14/16] t1400: " Trieu Huynh
2026-03-28 20:02 ` [GSoC PATCH 15/16] t0100: " Trieu Huynh
2026-03-28 20:02 ` [GSoC PATCH 16/16] t2206: " Trieu Huynh
2026-03-29 0:44 ` Junio C Hamano [this message]
2026-03-29 12:59 ` [GSoC PATCH 00/16] Microproject: " Trieu Huynh
2026-03-30 9:51 ` Karthik Nayak
2026-03-30 15:00 ` Junio C Hamano
2026-03-30 18:50 ` Trieu Huynh
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=xmqqpl4nh3b3.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=vikingtc4@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 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.