All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Tanga Joris <tangajoris@gmail.com>
Cc: git@vger.kernel.org,  l.s.r@web.de,  christian.couder@gmail.com,
	siddharthasthana31@gmail.com,  kaartic.sivaraam@gmail.com,
	usmanakinyemi202@gmail.com,  herroyalpriestess@gmail.com
Subject: Re: [Outreachy PATCH v5 1/3] parse-options: answer --git-completion-helper before command runs
Date: Thu, 05 Nov 2026 20:11:23 -0800	[thread overview]
Message-ID: <xmqqfqxeoaz8.fsf@gitster.g> (raw)
In-Reply-To: <20261105223458.1534785-1-tangajoris@gmail.com> (Tanga Joris's message of "Fri, 6 Nov 2026 01:34:56 +0300")

Tanga Joris <tangajoris@gmail.com> writes:

> +/*
> + * Programs that call parse_options() early do not need this function.
> + * If your program has to answer help requests (-h and --help-all) or
> + * the completion helper before parse_options() runs, call this
> + * function to answer them.
> + */
>  void show_usage_with_options_if_asked(int ac, const char **av,
>  				      const char * const *usage,
>  				      const struct option *options);

OK.  Let's mark the topic as ready for 'next'.

      parent reply	other threads:[~2026-11-06  4:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-24  5:24 [Outreachy PATCH] git.c: drop NO_PARSEOPT from builtins that use parse-options Tanga Joris
2026-10-25  7:59 ` René Scharfe
2026-10-26  2:59   ` Tanga Joris
2026-10-26  4:58     ` Junio C Hamano
2026-10-29  1:26 ` [Outreachy PATCH v2 1/2] fast-import: handle --git-completion-helper before reading input Tanga Joris
2026-10-29  1:26   ` [Outreachy PATCH v2 2/2] git.c: drop NO_PARSEOPT from builtins that use parse-options Tanga Joris
2026-10-29 18:04   ` [Outreachy PATCH v2 1/2] fast-import: handle --git-completion-helper before reading input Junio C Hamano
2026-10-29 23:16   ` [Outreachy PATCH v3 1/2] parse-options: answer --git-completion-helper before command runs Tanga Joris
2026-10-29 23:16     ` [Outreachy PATCH v3 2/2] git.c: drop NO_PARSEOPT from builtins that use parse-options Tanga Joris
2026-10-30 10:21       ` Kaartic Sivaraam
2026-11-02  2:26         ` Tanga Joris
2026-10-30  9:44     ` [Outreachy PATCH v3 1/2] parse-options: answer --git-completion-helper before command runs Kaartic Sivaraam
2026-10-31 22:01       ` Tanga Joris
2026-11-03  9:25     ` Cynthia Uche
2026-11-04 22:34       ` Tanga Joris
2026-11-05  0:39     ` [Outreachy PATCH v4 1/3] " Tanga Joris
2026-11-05  0:39       ` [Outreachy PATCH v4 2/3] git.c: drop NO_PARSEOPT from builtins that use parse-options Tanga Joris
2026-11-05  0:39       ` [Outreachy PATCH v4 3/3] t0012: catch builtins that keep NO_PARSEOPT after conversion Tanga Joris
2026-11-05 15:32       ` [Outreachy PATCH v4 1/3] parse-options: answer --git-completion-helper before command runs Junio C Hamano
2026-11-05 19:14         ` Tanga Joris
2026-11-05 22:34       ` [Outreachy PATCH v5 " Tanga Joris
2026-11-05 22:34         ` [Outreachy PATCH v5 2/3] git.c: drop NO_PARSEOPT from builtins that use parse-options Tanga Joris
2026-11-05 22:34         ` [Outreachy PATCH v5 3/3] t0012: catch builtins that keep NO_PARSEOPT after conversion Tanga Joris
2026-11-06  4:11         ` Junio C Hamano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqfqxeoaz8.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=herroyalpriestess@gmail.com \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=l.s.r@web.de \
    --cc=siddharthasthana31@gmail.com \
    --cc=tangajoris@gmail.com \
    --cc=usmanakinyemi202@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.