"Johannes Schindelin via GitGitGadget" <gitgitgad...@gmail.com> writes:
> Obviously, those `git-legacy-<command>` commands share the documentation > with the built-in `git-<command>`, and are not intended to be called > directly anyway. So let's not try to ensure that they are documented > separately from their built-in versions. Yup. This is the "other" loop that goes over the list of ALL_COMMANDS and makes sure each of them has its own documentation page. Looking good. > > Signed-off-by: Johannes Schindelin <johannes.schinde...@gmx.de> > --- > Makefile | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Makefile b/Makefile > index a5212c64bf..caa20923a4 100644 > --- a/Makefile > +++ b/Makefile > @@ -3074,7 +3074,7 @@ check-docs:: Documentation/GIT-EXCLUDED-PROGRAMS > git-merge-octopus | git-merge-ours | git-merge-recursive | \ > git-merge-resolve | git-merge-subtree | \ > git-fsck-objects | git-init-db | \ > - git-remote-* | git-stage | \ > + git-remote-* | git-stage | git-legacy-* | \ > git-?*--?* ) continue ;; \ > esac ; \ > test -f "Documentation/$$v.txt" || \
