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

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

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Sep 13, 2021, 11:19 UTC
Message-ID
<87r1ds4t3w.fsf@evledraar.gmail.com>
In-Reply-To
<d3635cbfd6ef0d47ebf28c516476dcd0b718afd4.1631531219.git.gitgitgadget@gmail.com>
On Mon, Sep 13 2021, Matthias Aßhauer via GitGitGadget wrote:
Show 5 quoted lines
> From: =?UTF-8?q?Matthias=20A=C3=9Fhauer?= <mha1993@live.de>
>
> While 'git version' is probably the least complex git command,
> it is a non-experimental user-facing builtin command. As such
> it should have a help page.
This looks good
Show 31 quoted lines
> Signed-off-by: Matthias Aßhauer <mha1993@live.de>
> ---
>  Documentation/git-version.txt | 35 +++++++++++++++++++++++++++++++++++
>  1 file changed, 35 insertions(+)
>  create mode 100644 Documentation/git-version.txt
>
> diff --git a/Documentation/git-version.txt b/Documentation/git-version.txt
> new file mode 100644
> index 00000000000..c7d6b496c8d
> --- /dev/null
> +++ b/Documentation/git-version.txt
> @@ -0,0 +1,35 @@
> +git-version(1)
> +==============
> +
> +NAME
> +----
> +git-version - Display version information about Git
> +
> +
> +SYNOPSIS
> +--------
> +[verse]
> +'git version' [--build-options]
>
> +
> +DESCRIPTION
> +-----------
> +
> +With no options given, the version of 'git' is printed
> +on the standard output.
Good
> +
> +If the option `--build-options` is given, information about how git was built is
> +printed on the standard output in addition to the version number.
Let's just cover this in the OPTIONS section you added...
> +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.
Show 9 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".

Or something like that, i.e. to cross-link the two.
Previous: Matthias Aßhauer via GitGitGadgetNext: Matthias Aßhauer
Message 7 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.