From: Phillip Wood <phillip.wood123@gmail.com>
To: kerylefondji7@gmail.com
Cc: git@vger.kernel.org, gitster@pobox.com,
christian.couder@gmail.com, siddharthasthana31@gmail.com
Subject: Re: [Outreachy][PATCH v3] builtin/var: refactor to use parse-options API
Date: Sun, 18 Oct 2026 16:09:15 +0100 [thread overview]
Message-ID: <e7719810-0e47-4031-a35a-9e1fd5727be4@gmail.com> (raw)
In-Reply-To: <20261018145222.579-1-kerylefondji7@gmail.com>
Hi Keryle
On 18/10/2026 15:52, kerylefondji7@gmail.com wrote:
> 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
next prev parent reply other threads:[~2026-10-18 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 14:52 [Outreachy][PATCH v3] builtin/var: refactor to use parse-options API kerylefondji7
2026-10-18 15:09 ` Phillip Wood [this message]
2026-10-18 20:55 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2026-10-18 15:29 kerylefondji7
2026-10-17 13:17 kerylefondji7
2026-10-18 9:45 ` Phillip Wood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e7719810-0e47-4031-a35a-9e1fd5727be4@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kerylefondji7@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=siddharthasthana31@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox