Re: [Outreachy PATCH v3 1/2] parse-options: answer --git-completion-helper before command runs

From
Tanga Joris <hidden>
Date
2026-10-31 22:02:06
Reply to
Kaartic Sivaraam, 2026-10-30
Hello Kaartic,

Thank you so much for taking the time to review this.

On Fri, 30 Oct 2026 at 12:44, Kaartic Sivaraam
[off-list ref] wrote:
Just a gentle reminder about this portion of the MyFirstContribution[1]:

   It’s good manners to reply to each comment in the mailing list
   discussion instead of letting the next version of your patch be your
   only response. Tell the reviewer whether you plan to make the
   suggested change, keep the original, or pursue a different approach.
Thanks for the reminder about replying to comments. I'll do that from
now on.
May be give a hint that you plan to do this in the following commit?
That might give someone without context (for example someone reading the
commit after a while) a hint about why you are worrying about marking
fast-import with the NO_PARSEOPT flag.
Alright, I'll add a sentence to the commit message saying that the
next commit removes the NO_PARSEOPT flag from fast-import, which would
make "git fast-import --<TAB>" freeze without this patch.
The change seems to be fine but I wonder if it is worth a note in
parse-options.h about why show_usage_with_options_if_asked() is also
handling the '--git-completion-helper' and '--git-completion-helper-all'
arguments?
Yes, I think that would help, so I will add a short comment above its
declaration in parse-options.h explaining that it answers these before
the command does any work.

Thanks,
Tanga
Thread (24 messages) 24 messages, 5 authors, last reply 2d ago
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help