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

Re: Git commands version documentation

From
Junio C Hamano <gitster@pobox.com>
Date
May 22, 2022, 23:35 UTC
Message-ID
<xmqqr14l87jp.fsf@gitster.g>
In-Reply-To
<f3814646-4763-62e1-b64e-d1aab3fdbbc8@iee.email>
Philip Oakley <philipoakley@iee.email> writes:
Show 6 quoted lines
> One manual method is to look at the history (blame) for the respective
> man pages to see when the man page was initially committed, and when
> appropriate options were added.
>
> Maybe use one of the hosting providers GUI if that is your choice e.g.
> https://github.com/git/git/blame/master/Documentation/git-gc.txt

I got an impression that blame/log is an overkill for the request, which asks for "what tagged version?", to which the answer would be to compare the manual pages for each release (or scan the release notes), perhaps?

Previous: Philip OakleyNext: Philip Oakley
Message 3 of 7 in “Git commands version documentation”
  1. Hrushikesh RaoMay 22, 2022
  2. Philip OakleyMay 22, 2022
  3. Junio C HamanoMay 22, 2022
  4. Philip OakleyMay 23, 2022
  5. Ævar Arnfjörð BjarmasonMay 23, 2022
  6. Philip OakleyMay 23, 2022
  7. Ævar Arnfjörð BjarmasonMay 23, 2022

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.