git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[Outreachy] Introduction: Tanga Joris, option parsing project

From
TJTanga Joris <tangajoris@gmail.com>
Date
Oct 20, 2026, 22:11 UTC
Message-ID
<CAKrRMNruH+eN9CVrdwfg563ceQp8bQwCDBkV7ex0h_=X3eOBdg@mail.gmail.com>
Resending in Plain text
Hi everyone,

My name is Tanga Joris. I'm a software engineer based in Nairobi, Kenya and I am about to graduate from university:)

I'm an Outreachy applicant for the December 2026 round, and I'd like to work on the project "Improve how command arguments and options are scanned and parsed". I am really sorry for starting late; I hope you are okay with that.

I've been interested in version control for a long time, and I've run into parsing problems in my own projects. In a CLI tool I built, a global --addr flag only works before the subcommand: "kiln run --addr x" fails because the subcommand's flag set doesn't know about it. I later noticed Git has the same rule, for example "git remote -v" has to come before the subcommand, and that got me curious about how Git scans and parses its arguments.

For my microproject, I'd like to convert the " ... and %d more." message in builtin/checkout.c (suggest_reattach()) from _() to Q_(). So far I haven't found anyone working on it in the archive, but please let me know if someone already is.

Thanks, Tanga

Next: Usman Akinyemi
Message 1 of 2 in “[Outreachy] Introduction: Tanga Joris, option parsing project”
  1. Tanga JorisOct 20, 2026
  2. Usman AkinyemiOct 22, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.