From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>
To: "Junio C Hamano" <gitster@pobox•com>
Cc: "Matěj Cepl" <mcepl@cepl•eu>,
"Jonas Konrad" <jonas.konrad@uni-muenster•de>,
git@vger•kernel.org, "Jeff King" <peff@peff•net>
Subject: Re: Git branch outputs usage message on stderr
Date: Wed, 15 Jan 2025 18:39:45 +0100 [thread overview]
Message-ID: <0cf0b268-c691-4fed-a58b-ea9f77eab295@app.fastmail.com> (raw)
In-Reply-To: <xmqq34hkyoys.fsf@gitster.g>
On Wed, Jan 15, 2025, at 18:19, Junio C Hamano wrote:
> "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com> writes:
>> [snip]
>
> Being consistent is a good idea, and I wanted to first gauge which
> way we should unify. It seems that those who spit their help text
> into their standard error stream are indeed in minority?
Yes: 40 of those stderr `-h` outputs.
Versus 102 that use stdout.[1]
Trying a random command with usage-on-error:
$ git-upload-pack >/dev/null
usage: [snip]
Does give usage on stderr.
† 1:
git add
git annotate
git apply
git archive
git bisect
git blame
git bugreport
git bundle
git cat-file
git check-attr
git check-ignore
git check-mailmap
git checkout
git cherry
git cherry-pick
git clean
git clone
git column
git commit-graph
git config
git count-objects
git credential-cache
git credential-cache--daemon
git credential-store
git describe
git diagnose
git difftool
git fast-export
git fetch
git fmt-merge-msg
git for-each-ref
git for-each-repo
git format-patch
git fsck
git fsck
git grep
git hash-object
git help
git hook
git init
git init
git interpret-trailers
git log
git ls-remote
git ls-tree
git mailinfo
git maintenance
git merge-base
git merge-file
git merge-tree
git mktag
git mktree
git multi-pack-index
git mv
git name-rev
git notes
git pack-objects
git pack-refs
git patch-id
git blame
git prune
git prune-packed
git pull
git push
git range-diff
git read-tree
git receive-pack
git reflog
git refs
git remote
git repack
git replace
git replay
git rerere
git reset
git restore
git revert
git rm
git send-pack
git shortlog
git log
git show-branch
git show-index
git show-ref
git sparse-checkout
git add
git stash
git stripspace
git submodule--helper
git switch
git symbolic-ref
git tag
git update-ref
git update-server-info
git-upload-pack
git verify-commit
git verify-pack
git verify-tag
git version
git log
git worktree
git write-tree
next prev parent reply other threads:[~2025-01-15 17:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 11:21 Git branch outputs usage message on stderr Jonas Konrad
2025-01-15 11:36 ` Matěj Cepl
2025-01-15 14:47 ` Jonas Konrad
2025-01-15 15:28 ` Junio C Hamano
2025-01-15 16:55 ` Kristoffer Haugsbakk
2025-01-15 17:14 ` Jeff King
2025-01-15 17:49 ` Junio C Hamano
2025-01-15 17:56 ` Junio C Hamano
2025-01-15 18:24 ` Jeff King
2025-01-15 21:16 ` Junio C Hamano
2025-01-15 21:29 ` Jeff King
2025-01-15 21:56 ` Junio C Hamano
2025-01-15 22:27 ` Jeff King
2025-01-15 23:32 ` Junio C Hamano
2025-01-16 1:21 ` Junio C Hamano
2025-01-16 10:24 ` Jeff King
2025-01-15 22:11 ` Junio C Hamano
2025-01-15 22:28 ` Jeff King
2025-01-15 23:35 ` Junio C Hamano
2025-01-15 18:29 ` Junio C Hamano
2025-01-15 18:33 ` Kristoffer Haugsbakk
2025-01-15 21:13 ` Junio C Hamano
2025-01-15 17:14 ` Jonas Konrad
2025-01-15 17:53 ` Kristoffer Haugsbakk
2025-01-15 17:19 ` Junio C Hamano
2025-01-15 17:39 ` Kristoffer Haugsbakk [this message]
2025-01-15 17:47 ` Junio C Hamano
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=0cf0b268-c691-4fed-a58b-ea9f77eab295@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=jonas.konrad@uni-muenster$(echo .)de \
--cc=mcepl@cepl$(echo .)eu \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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