threads / patch / 66575

v3Re: [Outreachy][PATCH v3] builtin/var: refactor to use parse-options API

Subject: Re: [Outreachy][PATCH v3] builtin/var: refactor to use parse-options API

## tl;dr

3 messages between Oct 18, 2026 and Oct 18, 2026. Diffs are folded; open one to read it.

replies: 2people: 3as markdown or json

kerylefondji7@gmail.com· Oct 18, 2026, 14:52 UTC · lore
From: Keryle Fondji <kerylefondji7@gmail.com>
Hi Phillip,
Thank you very much for reviewing my patch and for pointing this out! I didn't realize that `git var` had already been converted.
I am new to open source and to this ecosystem, so I am still getting familiar with how everything works. Could you please advise on where I can find a list of available microprojects or files to work on, to make sure I don't pick something that is already done?
Thank you again for your guidance and patience.

Best regards, Keryle

Phillip Wood· Oct 18, 2026, 15:09 UTC · re: kerylefondji7@gmail.com · lore
Hi Keryle
On 18/10/2026 15:52, kerylefondji7@gmail.com wrote:
Show 8 quoted lines
> From: Keryle Fondji <kerylefondji7@gmail.com>
> > Hi Phillip,
> > Thank you very much for reviewing my patch and for pointing this out!
> I didn't realize that `git var` had already been converted.>
> I am new to open source and to this ecosystem, so I am still getting
> familiar with how everything works. Could you please advise on where I
> can find a list of available microprojects or files to work on, to
> make sure I don't pick something that is already done?
There are suggestions for microprojects at [1] and some additional guidance at [2]. The test conversions are a good way to get familiar with our test suite. To check you're not working on the same thing as someone else you should scan the mailing list archives [3] and/or see what is in the "seen" branch. In many ways the main point of a microproject is to get candidates familiar with sending patches to the mailing list and interacting with reviewers. You've shown that you understand how to send patches, respond to comments and ask for help even if this particular patch (which looked very sensible) did not end up being merged.
Thanks
Phillip

[1] https://git.github.io/SoC-2026-Microprojects/ [2] https://git.github.io/General-Microproject-Information/ [3] https://lore.kernel.org/git

> Thank you again for your guidance and patience.
> > Best regards,
> Keryle
Junio C Hamano· Oct 18, 2026, 20:55 UTC · re: Phillip Wood · lore
Phillip Wood <phillip.wood123@gmail.com> writes:
> ... In many ways the main point of a 
> microproject is to get candidates familiar with sending patches to the 
> mailing list and interacting with reviewers.
Thanks for highlighting this important point.  Highly appreciated.

← back to recent threads