From: Trieu Huynh <vikingtc4@gmail.com>
Date: Sun, 29 Mar 2026 12:59:21 GMT
Subject: Re: [GSoC PATCH 00/16] Microproject: avoid suppressing git's exit code
Message-ID: <ftwnrutdbvyf7phr4ad76agt2jvzgieqnxprvmoyw2vzwbhgqy@z4x2g2n3ft4r>
In-Reply-To: <xmqqpl4nh3b3.fsf@gitster.g>

On Sat, Mar 28, 2026 at 05:44:48PM -0700, Junio C Hamano wrote:
> 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.
Ack, I missed that point. Could you clarify how many patches or
files changed are considered appropriate for the microproject?

BRs,