Re: [Outreachy] Git command argument parsing micro-project
- From
Usman Akinyemi <usmanakinyemi202@gmail.com>
- Date
- Oct 21, 2026, 14:37 UTC
- Message-ID
- <CAPSxiM9_7LWD6_L5Wsh9LV60FwQxxgLgOSaHQ4QfraZ1PjjV5w@mail.gmail.com>
- In-Reply-To
- <CAPki72GYsid5DqaP8urq-gVrNEvMZM+sXUaNjir-VXc+qokMfw@mail.gmail.com>
On Wed, Oct 21, 2026 at 2:22 PM Azuama Odinaka Maximus <azuama69@gmail.com> wrote:
Show 6 quoted lines
> > Hello Git community, > > My name is Azuama Odinaka Maximus, and I am an Outreachy applicant > interested in the project “Improve how command arguments and options > are scanned and parsed.”
Hello Azuama, Welcome to the Git project.
> > I am a beginner in C and am learning to contribute to Git by studying > its codebase, reproducing issues, and writing tests.
Thanks for your interest in the Git project.
Show 9 quoted lines
> > I have prepared a small patch for builtin/rev-list.c to prevent the > early option scan from interpreting the argument to --grep as another > option. I also added a regression test in t/t6022-rev-list-missing.sh. > The relevant test suite passes locally. > > I would appreciate feedback on whether this is an appropriate > micro-project contribution and whether the fix should be improved to > handle this class of argument-parsing issues more generally.
It is a good microproject. Since you already said, you worked on something already, send for review and for microproject. We can then see if there is a follow up.
Show 5 quoted lines
> > Thank you for your time and for supporting Outreachy applicants. > > Best regards, > Azuama Odinaka Maximus
Thanks. Usman.
>