Re: [Outreachy] Applicant Introduction

From: Usman Akinyemi <usmanakinyemi202@gmail.com>
Date: Oct 22, 2026, 09:54 UTC
Message-ID: <CAPSxiM8Nv5mnWoFVjWE284yhYG0rdLmfXN2xbZpm4H-wO7oAng@mail.gmail.com>
In-Reply-To: <CAOcE0w+EciSBZDTTNzbi8hEzZAZjB6gut=Pc9qB5yEgs-w1f2g@mail.gmail.com>

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

Hi Priestess,

Show 6 quoted lines

>
> 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

mpare the file, changing only those four spots.

Show 15 quoted lines

>
> 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.

Next time, you do not have to wait for someone to tell you to proceed, you can send your patch when you have checked that no one is working on it. You can also indicate that you are working on it after ensuring no other patches addressing the problem.

For "indicating that you want to work on a patch", that is needed if there was a discussion on solving the problem before or it is a leftoverbits.

>
> Thanks,
> Cynthia

Thanks.

Usman.