Jeff Hostetler <git@xxxxxxxxxxxxxxxxx> writes: > I'd rather not use the term "subcommand" because it already has mixed > usage. > [] See git_more_info_string[] in git.c and list_all_cmd_help() > in help.c where both "command" and "subcommand" are used > interchangeably. > [] And yet another completely different usage in git-submodule > and bisect where "subcommand" is used to mean the 3rd token > on the command line after the "command". To "git" the command, "submodule" would be its direct subcommand, and to "git submodule", things like "update", "init", etc. are subcommands that is one level down. I am not sure if it bothers me too much that hierarchical things are not always named from the top-level, requiring the third-level things to be called always subsubX. In the context of describing "git submodule", I would say calling "init" subsubcommand may be technically correct, but it would be too pedantic to be practical, when it is clear from the context that we are discussing "git submodule".
