summaryrefslogtreecommitdiff
path: root/t
diff options
context:
space:
mode:
authorTaylor Blau <me@ttaylorr.com>2021-03-30 15:04:04 (GMT)
committerJunio C Hamano <gitster@pobox.com>2021-03-30 19:16:56 (GMT)
commitcd57bc41bbcc8d260040243946d19075eff0bfaf (patch)
treebcf1217018b0dc0ff1d5497673e01e5f64aebe7c /t
parent690eb057198275b314b776688240fcc7f9e789d0 (diff)
downloadgit-cd57bc41bbcc8d260040243946d19075eff0bfaf.zip
git-cd57bc41bbcc8d260040243946d19075eff0bfaf.tar.gz
git-cd57bc41bbcc8d260040243946d19075eff0bfaf.tar.bz2
builtin/multi-pack-index.c: display usage on unrecognized command
When given a sub-command that it doesn't understand, 'git multi-pack-index' dies with the following message: $ git multi-pack-index bogus fatal: unrecognized subcommand: bogus Instead of 'die()'-ing, we can display the usage text, which is much more helpful: $ git.compile multi-pack-index bogus error: unrecognized subcommand: bogus usage: git multi-pack-index [<options>] write or: git multi-pack-index [<options>] verify or: git multi-pack-index [<options>] expire or: git multi-pack-index [<options>] repack [--batch-size=<size>] --object-dir <file> object directory containing set of packfile and pack-index pairs --progress force progress reporting While we're at it, clean up some duplication between the "no sub-command" and "unrecognized sub-command" conditionals. Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Signed-off-by: Taylor Blau <me@ttaylorr.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't')
0 files changed, 0 insertions, 0 deletions