{"thread":{"id":"66609","subject":"[Outreachy] Introduction: Tanga Joris, option parsing project","startedAt":"2026-10-20T22:11:50Z","lastAt":"2026-10-22T10:01:01Z","messageCount":2,"participants":["Tanga Joris","Usman Akinyemi"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"555632","messageId":"CAKrRMNruH+eN9CVrdwfg563ceQp8bQwCDBkV7ex0h_=X3eOBdg@mail.gmail.com","threadId":"66609","inReplyTo":null,"subject":"[Outreachy] Introduction: Tanga Joris, option parsing project","fromName":"Tanga Joris","fromEmail":"tangajoris@gmail.com","sentAt":"2026-10-20T22:11:50Z","receivedAt":"2026-10-20T22:11:50Z","isPatch":false,"sender":{"key":"tangajoris@gmail.com","avatar":null},"body":"Resending in Plain text\n\nHi everyone,\n\nMy name is Tanga Joris. I'm a software engineer based in\nNairobi, Kenya and I am about to graduate from university:)\n\nI'm an Outreachy applicant for the December 2026 round, and I'd like\nto work on the project \"Improve how command arguments and options\nare scanned and parsed\". I am really sorry for starting late; I hope\nyou are okay with that.\n\nI've been interested in version control for a long time, and I've run\ninto parsing problems in my own projects. In a CLI tool I built, a\nglobal --addr flag only works before the subcommand: \"kiln run --addr\nx\" fails because the subcommand's flag set doesn't know about it. I\nlater noticed Git has the same rule, for example \"git remote -v\" has\nto come before the subcommand, and that got me curious about how Git\nscans and parses its arguments.\n\nFor my microproject, I'd like to convert the \" ... and %d more.\"\nmessage in builtin/checkout.c (suggest_reattach()) from _() to Q_().\nSo far I haven't found anyone working on it in the archive, but please\nlet me know if someone already is.\n\nThanks,\nTanga\n\n"},{"id":"555842","messageId":"CAPSxiM_eZ62ExDaqjehSEm37c1EhU=P4kL_kpobWj_RAD5zewg@mail.gmail.com","threadId":"66609","inReplyTo":"CAKrRMNruH+eN9CVrdwfg563ceQp8bQwCDBkV7ex0h_=X3eOBdg@mail.gmail.com","subject":"Re: [Outreachy] Introduction: Tanga Joris, option parsing project","fromName":"Usman Akinyemi","fromEmail":"usmanakinyemi202@gmail.com","sentAt":"2026-10-22T10:01:01Z","receivedAt":"2026-10-22T10:01:01Z","isPatch":false,"sender":{"key":"usmanakinyemi202@gmail.com","avatar":"https://avatars.githubusercontent.com/u/86585626?v=4"},"body":"On Tue, Oct 20, 2026 at 11:15 PM Tanga Joris <tangajoris@gmail.com> wrote:\n>\n> Resending in Plain text\n>\n> Hi everyone,\n>\n> My name is Tanga Joris. I'm a software engineer based in\n> Nairobi, Kenya and I am about to graduate from university:)\nWelcome Tanga,\n>\n> I'm an Outreachy applicant for the December 2026 round, and I'd like\n> to work on the project \"Improve how command arguments and options\n> are scanned and parsed\". I am really sorry for starting late; I hope\n> you are okay with that.\n>\nThanks for your interest at Git project. There is no problem with that at all.\nGit is open to contribution everytime.\n> I've been interested in version control for a long time, and I've run\n> into parsing problems in my own projects. In a CLI tool I built, a\n> global --addr flag only works before the subcommand: \"kiln run --addr\n> x\" fails because the subcommand's flag set doesn't know about it. I\n> later noticed Git has the same rule, for example \"git remote -v\" has\n> to come before the subcommand, and that got me curious about how Git\n> scans and parses its arguments.\n>\n> For my microproject, I'd like to convert the \" ... and %d more.\"\n> message in builtin/checkout.c (suggest_reattach()) from _() to Q_().\n> So far I haven't found anyone working on it in the archive, but please\n> let me know if someone already is.\nYou can work on it if you already noticed that no one is working on it.\n>\n> Thanks,\n> Tanga\nThanks.\nUsman.\n>\n\n"}]}