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

Re: [Outreachy PATCH] git.c: drop NO_PARSEOPT from builtins that use parse-options

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 26, 2026, 04:58 UTC
Message-ID
<xmqq33ttvz0q.fsf@gitster.g>
In-Reply-To
<CAKrRMNqtqYiE2YKVky+mHyrkqtW2c_L_DcCen1hyaQa8D0+fWw@mail.gmail.com>
Tanga Joris <tangajoris@gmail.com> writes:
> Christian, I plan to base it on top of your early-scan series, since
> it touches the same code. Would you be fine with that?

It is not something Christian can approve, nor do you need his permission.

You need to make sure that the topic you plan to depend on is as solid as possible. Those who write topics that depend on other topics usually make sure the topics they depend on are at least in 'next'.

You know how you can help make Christian's 'cc/early-scan-options' topic as solid as possible and help it get merged to 'next' sooner, right? In this community, topics do not move forward without positive reviews. As a potential user of the service the topic offers, you are in a better position than random bystanders to carefully review it, find issues, and offer improvements.

Thanks.
Previous: Tanga JorisNext: Tanga Joris
Message 4 of 13 in “git.c: drop NO_PARSEOPT from builtins that use parse-options”
  1. git.c: drop NO_PARSEOPT from builtins that use parse-optionsTanga Joris, Oct 24, 2026
  2. René ScharfeOct 25, 2026
  3. Tanga JorisOct 26, 2026
  4. Junio C HamanoOct 26, 2026
  5. 1/2 fast-import: handle --git-completion-helper before reading inputTanga Joris, Oct 29, 2026
  6. 2/2 git.c: drop NO_PARSEOPT from builtins that use parse-optionsTanga Joris, Oct 29, 2026
  7. Junio C HamanoOct 29, 2026
  8. 1/2 parse-options: answer --git-completion-helper before command runsTanga Joris, Oct 29, 2026
  9. 2/2 git.c: drop NO_PARSEOPT from builtins that use parse-optionsTanga Joris, Oct 29, 2026
  10. Kaartic SivaraamOct 30, 2026
  11. Tanga JorisNov 2, 2026
  12. Kaartic SivaraamOct 30, 2026
  13. Tanga JorisOct 31, 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.