threads / discuss / 66525

Re: [Outreachy] Applicant Introduction

Subject: Re: [Outreachy] Applicant Introduction

## tl;dr

6 messages between Oct 13, 2026 and Oct 26, 2026.

replies: 5people: 2as markdown or json

Usman Akinyemi· Oct 13, 2026, 22:33 UTC · lore
> Hello, everyone!
> 🙋🏽‍♀️
>
> My name is Cynthia, but you can call me Priestess.
Hello Cynthia,
>
> My pronouns are she/her.
>
> I've been accepted into the contribution phase of Outreachy December 2026 internship round.
Congratulations for getting accepted to the contribution stage.
>
> I'm interested in contributing to the Git community.
Thanks for your interest in the Git project.
> I've just read through the general microproject information documentation. I'm going through the materials for developing git, and I have just attempted to build git from source.
> I hope to get started on a microproject soon.
Yep.
>
> Looking forward to learning something exciting!
Definitely.

Thanks. Usman.

Priestess· Oct 19, 2026, 22:45 UTC · re: Usman Akinyemi · lore
(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

Usman Akinyemi· Oct 22, 2026, 09:54 UTC · re: Priestess · lore
>
> (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.
Priestess· Oct 23, 2026, 11:08 UTC · re: Usman Akinyemi · lore
> 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.
Hi Usman,
Thank you for the advice, I will keep that in mind next time.

I sent the patch the next day, and Patrick reviewed it and said it looks good to him. It is here:

https://lore.kernel.org/git/20261021033723.5265-1-herroyalpriestess@gmail.com/

If you have time, I would appreciate it if you could take a look at it as well.

Thanks, Cynthia

Usman Akinyemi· Oct 26, 2026, 20:34 UTC · re: Priestess · lore
> https://lore.kernel.org/git/20261021033723.5265-1-herroyalpriestess@gmail.com/
>
> If you have time, I would appreciate it if you could take a look
> at it as well.
Since Patrick already took a look at it already, it is more than ok.
And there is not need for me to take a look at it again.
>
> Thanks,
> Cynthia

← back to recent threads