mirror of
https://github.com/git/git
synced 2024-10-30 04:01:21 +00:00
c39fffc1c9
There's been a lot of incremental effort to make the SYNOPSIS output in our documentation consistent with the -h output, e.g.cbe485298b(git reflog [expire|delete]: make -h output consistent with SYNOPSIS, 2022-03-17) is one recent example, but that effort has been an uphill battle due to the lack of regression testing. This adds such regression testing, we can parse out the SYNOPSIS output with "sed", and it turns out it's relatively easy to normalize it and the "-h" output to match on another. We now ensure that we won't have regressions when it comes to the list of commands in "expect_help_to_match_txt" below, and in subsequent commits we'll make more of them consistent. The naïve parser here gets quite a few things wrong, but it doesn't need to be perfect, just good enough that we can compare /some/ of this help output. There's no cases where the output would match except for the parser's stupidity, it's all cases of e.g. comparing the *.txt to non-parse_options() output. Since that output is wildly different than the *.txt anyway let's leave this for now, we can fix the parser some other time, or it won't become necessary as we'll e.g. convert more things to using parse_options(). Having a special-case for "merge-tree"'s1f0c3a29da(merge-tree: implement real merges, 2022-06-18) is a bit ugly, but preferred to blessing that " (deprecated)" pattern for other commands. We'd probably want to add some other way of marking deprecated commands in the SYNOPSIS syntax. Syntactically 1f0c3a29da3's way of doing it is indistinguishable from the command taking an optional literal "deprecated" string as an argument. Some of the issues that are left: * "git show -h", "git whatchanged -h" and "git reflog --oneline -h" all showing "git log" and "git show" usage output. I.e. the "builtin_log_usage" in builtin/log.c doesn't take into account what command we're running. * Commands which implement subcommands such as like "multi-pack-index", "notes", "remote" etc. having their subcommands in a very different order in the *.txt and *.c. Fixing it would require some verbose diffs, so it's been left alone for now. * Commands such as "format-patch" have a very long argument list in the *.txt, but just "[<options>]" in the *.c. What to do about these has been left out of this series, except to the extent that preceding commits changed "[<options>]" (or equivalent) to the list of options in cases where that list of options was tiny, or we clearly meant to exhaustively list the options in both *.txt and *.c. Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
58 lines
557 B
Text
58 lines
557 B
Text
add
|
|
am
|
|
apply
|
|
archive
|
|
bisect
|
|
blame
|
|
branch
|
|
check-ref-format
|
|
checkout
|
|
checkout-index
|
|
clone
|
|
column
|
|
config
|
|
credential
|
|
credential-cache
|
|
credential-store
|
|
fast-export
|
|
fast-import
|
|
fetch-pack
|
|
fmt-merge-msg
|
|
for-each-ref
|
|
format-patch
|
|
fsck-objects
|
|
fsmonitor--daemon
|
|
gc
|
|
grep
|
|
index-pack
|
|
init-db
|
|
log
|
|
ls-files
|
|
ls-tree
|
|
mailinfo
|
|
mailsplit
|
|
maintenance
|
|
merge
|
|
merge-file
|
|
merge-index
|
|
merge-one-file
|
|
multi-pack-index
|
|
name-rev
|
|
notes
|
|
pack-objects
|
|
push
|
|
range-diff
|
|
rebase
|
|
remote
|
|
remote-ext
|
|
remote-fd
|
|
repack
|
|
reset
|
|
restore
|
|
rev-parse
|
|
show
|
|
stage
|
|
switch
|
|
update-index
|
|
update-ref
|
|
whatchanged
|