From: Priestess <herroyalpriestess@gmail.com>
Date: Mon, 19 Oct 2026 22:45:02 GMT
Subject: Re: [Outreachy] Applicant Introduction
Message-ID: <CAOcE0w+EciSBZDTTNzbi8hEzZAZjB6gut=Pc9qB5yEgs-w1f2g@mail.gmail.com>
In-Reply-To: <CAPSxiM-dxHUE5tHf830=zHnLfg1U5jyb211-ZODS7bu8OjqEnw@mail.gmail.com>

(Resending in plain text, since my first mail was rejected by the list.)

Hi everyone,

I hope you're doing well.

(Thank you for your welcome, Usman.)

For my microproject, I'd like to work on avoiding suppressed git exit
codes in test scripts, in t/t2104-update-index-skip-worktree.sh.

In that script, `git ls-files -t` is piped into `test_cmp` in four
places (the 'setup', 'update-index --skip-worktree', 'ls-files -t' and
'update-index --no-skip-worktree' tests). If `git ls-files` crashed,
the test would still pass. I plan to write the output to a file first
and compare the file, changing only those four spots.

To check that nobody else is on this file, I did the following:

 + I searched lore for "t2104" and "update-index-skip-worktree" and
   found no recent patches touching it
 + I ran `git log` on the file against origin/master, origin/next and
   origin/seen and found nothing in flight
 + I also checked GitGitGadget pull requests & issues for "t2104"

I found a GSoC 2024 attempt on this file but I could not find that it
was merged. Also, Junio's "t2104: style fixes" commit did not
change these pipe lines. So, I believe the exit code issue is still
there.

I'd like to know if I'm clear to proceed with a patch.

Thanks,
Cynthia