From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH v5 0/6] Send help text from "git cmd -h" to stdout
Date: Fri, 17 Jan 2025 13:31:42 -0800 [thread overview]
Message-ID: <20250117213148.3974552-1-gitster@pobox.com> (raw)
In-Reply-To: <20250116213553.2563751-1-gitster@pobox.com>
Jonas Konrad noticed[*] that "git branch -h" started showing the help
text to the standard error stream. It turns out that we are fairly
inconsistent in our implementation of "git cmd -h". The users of
parse-options API will get "If -h is the only option on the command
line, give the help text to the standard output" for free, but some
commands manually check for the condition and then call the
usage_with_options() function, which gives the identical help text
to the standard error stream. And "git branch -h" Jonas noticed was
one of them.
Older commands written before parse-options API became dominant show
the help text by calling the usage() function, which is meant to be
used when they fail to parse their command line arguments, which has
the same problem. An explicit request for help text "git cmd -h"
should be fulfilled by showing the help on the standard output.
This series teachs "git $cmd -h" to send its help text to the
standard output stream consistently for built-in commands.
There is a related "what status should these command exit with?"
question, and an argument can be made to switch them to exit with 0,
instead of historical 129, but it is left outside of the series for
now.
Changes since v4:
- vfdreportf() helper that took a file descriptor has been replaced
with vfreportf() that takes a FILE * instead, with Peff's help.
[Reference]
https://lore.kernel.org/git/04cfaa3b-847f-4850-9dd6-c1cf9f72807f@uni-muenster.de/
Jeff King (1):
t0012: optionally check that "-h" output goes to stdout
Junio C Hamano (5):
parse-options: add show_usage_with_options_if_asked()
usage: add show_usage_if_asked()
builtins: send usage_with_options() help text to standard output
oddballs: send usage() help text to standard output
builtin: send usage() help text to standard output
builtin/am.c | 3 +--
builtin/branch.c | 4 ++--
builtin/check-ref-format.c | 4 ++--
builtin/checkout--worker.c | 6 +++---
builtin/checkout-index.c | 6 +++---
builtin/commit-tree.c | 4 ++--
builtin/commit.c | 8 ++++----
builtin/credential.c | 3 ++-
builtin/diff-files.c | 3 +--
builtin/diff-index.c | 3 +--
builtin/diff-tree.c | 3 +--
builtin/fast-import.c | 3 +--
builtin/fetch-pack.c | 2 ++
builtin/fsmonitor--daemon.c | 4 ++--
builtin/gc.c | 4 ++--
builtin/get-tar-commit-id.c | 4 +++-
builtin/index-pack.c | 3 +--
builtin/ls-files.c | 4 ++--
builtin/mailsplit.c | 4 ++--
builtin/merge-index.c | 7 ++++++-
builtin/merge-ours.c | 3 +--
builtin/merge-recursive.c | 6 ++++++
builtin/merge.c | 4 ++--
builtin/pack-redundant.c | 3 +--
builtin/rebase.c | 6 +++---
builtin/remote-ext.c | 2 ++
builtin/remote-fd.c | 1 +
builtin/rev-list.c | 3 +--
builtin/rev-parse.c | 2 ++
builtin/unpack-file.c | 8 ++++++--
builtin/unpack-objects.c | 2 ++
builtin/update-index.c | 4 ++--
builtin/upload-archive.c | 6 +++---
builtin/var.c | 1 +
git-compat-util.h | 2 ++
parse-options.c | 10 ++++++++++
parse-options.h | 4 ++++
t/helper/test-simple-ipc.c | 4 ++--
t/t0012-help.sh | 3 ++-
t/t7600-merge.sh | 2 +-
usage.c | 27 ++++++++++++++++++++++++---
41 files changed, 121 insertions(+), 64 deletions(-)
--
2.48.1-218-gc7e8be6a8f
next prev parent reply other threads:[~2025-01-17 21:31 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 1:25 [PATCH v3 0/6] Send help text from "git cmd -h" to stdout Junio C Hamano
2025-01-16 1:25 ` [PATCH v3 1/6] parse-options: add show_usage_help_and_exit_if_asked() Junio C Hamano
2025-01-16 1:25 ` [PATCH v3 2/6] t0012: optionally check that "-h" output goes to stdout Junio C Hamano
2025-01-16 1:25 ` [PATCH v3 3/6] builtins: send usage_with_options() help text to standard output Junio C Hamano
2025-01-16 1:25 ` [PATCH v3 4/6] usage: add show_usage_and_exit_if_asked() Junio C Hamano
2025-01-16 10:36 ` Jeff King
2025-01-16 10:44 ` Jeff King
2025-01-16 17:22 ` Junio C Hamano
2025-01-16 21:54 ` Jeff King
2025-01-16 22:26 ` Junio C Hamano
2025-01-16 1:25 ` [PATCH v3 5/6] oddballs: send usage() help text to standard output Junio C Hamano
2025-01-16 10:42 ` Jeff King
2025-01-16 17:24 ` Junio C Hamano
2025-01-16 1:25 ` [PATCH v3 6/6] builtin: " Junio C Hamano
2025-01-16 17:30 ` Junio C Hamano
2025-01-16 20:37 ` Junio C Hamano
2025-01-16 10:46 ` [PATCH v3 0/6] Send help text from "git cmd -h" to stdout Jeff King
2025-01-16 17:28 ` Junio C Hamano
2025-01-16 21:35 ` [PATCH v4 " Junio C Hamano
2025-01-16 21:35 ` [PATCH v4 1/6] t0012: optionally check that "-h" output goes " Junio C Hamano
2025-01-16 21:35 ` [PATCH v4 2/6] parse-options: add show_usage_with_options_if_asked() Junio C Hamano
2025-01-16 21:35 ` [PATCH v4 3/6] usage: add show_usage_if_asked() Junio C Hamano
2025-01-16 23:00 ` Junio C Hamano
2025-01-17 11:41 ` Jeff King
2025-01-16 21:35 ` [PATCH v4 4/6] builtins: send usage_with_options() help text to standard output Junio C Hamano
2025-01-16 21:35 ` [PATCH v4 5/6] oddballs: send usage() " Junio C Hamano
2025-01-16 21:35 ` [PATCH v4 6/6] builtin: " Junio C Hamano
2025-01-17 11:42 ` Jeff King
2025-01-17 19:46 ` Junio C Hamano
2025-01-17 21:31 ` Junio C Hamano [this message]
2025-01-17 21:31 ` [PATCH v5 1/6] t0012: optionally check that "-h" output goes to stdout Junio C Hamano
2025-01-17 21:31 ` [PATCH v5 2/6] parse-options: add show_usage_with_options_if_asked() Junio C Hamano
2025-01-17 21:31 ` [PATCH v5 3/6] usage: add show_usage_if_asked() Junio C Hamano
2025-01-17 21:31 ` [PATCH v5 4/6] builtins: send usage_with_options() help text to standard output Junio C Hamano
2025-01-17 21:31 ` [PATCH v5 5/6] oddballs: send usage() " Junio C Hamano
2025-01-17 21:31 ` [PATCH v5 6/6] builtin: " Junio C Hamano
2025-01-18 11:42 ` [PATCH v5 0/6] Send help text from "git cmd -h" to stdout Jeff King
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=20250117213148.3974552-1-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).