git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 2/2] documentation: add documentation for 'git version'

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 13, 2021, 19:43 UTC
Message-ID
<xmqq4kaofehr.fsf@gitster.g>
In-Reply-To
<87r1ds4t3w.fsf@evledraar.gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
Show 9 quoted lines
>> +Note that `git --version` is identical to `git version` because the
>> +former is internally converted into the latter.
>
> Probably better to just have a new section:
>
> SEE ALSO
> --------
>
> linkgit:git[1]'s `--version` option, which dispatches to this command.
Hmph, I am not sure if this is a good move.

If we are not giving any more information than what the reader has already learned from this page, other than "git --version" does the same thing, we probably do not want to do this. By seeing also that other page, the user will not learn anything new about "git version".

If a related "git --version-something-else" is described over there and may fill the need the reader had when visiting this page, that is a different story, but I do not think it is the case.

Show 17 quoted lines
>> +OPTIONS
>> +-------
>> +--build-options::
>> +	Prints out additional information about how git was built for diagnostic
>> +	purposes.
>> +
>> +GIT
>> +---
>> +Part of the linkgit:git[1] suite
>
>
> It would also be good to update git.txt, which now says:
>
>     Prints the Git suite version that the git program came from
>
> To say e.g. "Dispatches to linkgit:git-version[1], prints the git
> program version".
This one may be a good idea, I think.

"git --version --build-options" also works and we do not want to clutter git[1] with descriptions on suboptions of "git version".

If we are not doing so for the "--help" option in git[1], we should do so as well.

Thanks.
Previous: Matthias AßhauerNext: Matthias Aßhauer via GitGitGadget
Message 9 of 14 in “documentation: handle non-existing html pages and document 'git version'”
  1. 0/2 documentation: handle non-existing html pages and document 'git version'Matthias Aßhauer via GitGitGadget, Sep 13, 2021
  2. 1/2 help: make sure local html page exists before calling external processesMatthias Aßhauer via GitGitGadget, Sep 13, 2021
  3. Eric SunshineSep 13, 2021
  4. Matthias AßhauerSep 13, 2021
  5. Junio C HamanoSep 13, 2021
  6. 2/2 documentation: add documentation for 'git version'Matthias Aßhauer via GitGitGadget, Sep 13, 2021
  7. Ævar Arnfjörð BjarmasonSep 13, 2021
  8. Matthias AßhauerSep 13, 2021
  9. Junio C HamanoSep 13, 2021
  10. 0/2 documentation: handle non-existing html pages and document 'git version'Matthias Aßhauer via GitGitGadget, Sep 14, 2021
  11. 1/2 help: make sure local html page exists before calling external processesMatthias Aßhauer via GitGitGadget, Sep 14, 2021
  12. 2/2 documentation: add documentation for 'git version'Matthias Aßhauer via GitGitGadget, Sep 14, 2021
  13. Is "make check-docs" useful anymore?Ævar Arnfjörð Bjarmason, Sep 24, 2021
  14. Junio C HamanoSep 24, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.