From: Trieu Huynh <vikingtc4@gmail.com>
To: git@vger.kernel.org
Cc: Trieu Huynh <vikingtc4@gmail.com>
Subject: [GSoC PATCH 00/16] Microproject: avoid suppressing git's exit code
Date: Sun, 29 Mar 2026 05:02:39 +0900 [thread overview]
Message-ID: <20260328200255.247759-1-vikingtc4@gmail.com> (raw)
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
Trieu Huynh (16):
t7004: avoid suppressing git's exit code
t6423: avoid suppressing git's exit code
t6411: avoid suppressing git's exit code
t6101: avoid suppressing git's exit code
t6006: avoid suppressing git's exit code
t5304: avoid suppressing git's exit code
t4153: avoid suppressing git's exit code
t4150: avoid suppressing git's exit code
t4140: avoid suppressing git's exit code
t4039: avoid suppressing git's exit code
t3903: avoid suppressing git's exit code
t3701: avoid suppressing git's exit code
t3412: avoid suppressing git's exit code
t1400: avoid suppressing git's exit code
t0100: avoid suppressing git's exit code
t2206: avoid suppressing git's exit code
t/t0100-previous.sh | 3 +-
t/t1400-update-ref.sh | 3 +-
t/t2206-add-submodule-ignored.sh | 45 +++++++++++++++++++----------
t/t3412-rebase-root.sh | 6 ++--
t/t3701-add-interactive.sh | 12 +++++---
t/t3903-stash.sh | 5 ++--
t/t4039-diff-assume-unchanged.sh | 3 +-
t/t4140-apply-ita.sh | 3 +-
t/t4150-am.sh | 5 ++--
t/t4153-am-resume-override-opts.sh | 3 +-
t/t5304-prune.sh | 3 +-
t/t6006-rev-list-format.sh | 3 +-
t/t6101-rev-parse-parents.sh | 3 +-
t/t6411-merge-filemode.sh | 6 ++--
t/t6423-merge-rename-directories.sh | 3 +-
t/t7004-tag.sh | 6 ++--
16 files changed, 74 insertions(+), 38 deletions(-)
--
2.43.0
next reply other threads:[~2026-03-28 20:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 20:02 Trieu Huynh [this message]
2026-03-28 20:02 ` [GSoC PATCH 01/16] t7004: avoid suppressing git's exit code 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 ` [GSoC PATCH 00/16] Microproject: " Junio C Hamano
2026-03-29 12:59 ` 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=20260328200255.247759-1-vikingtc4@gmail.com \
--to=vikingtc4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox