From: Junio C Hamano <gitster@pobox.com>
To: Philip Oakley <philipoakley@iee.email>
Cc: Hrushikesh Rao <hrushikesh20thegreat@gmail.com>, git@vger.kernel.org
Subject: Re: Git commands version documentation
Date: Sun, 22 May 2022 16:35:38 -0700 [thread overview]
Message-ID: <xmqqr14l87jp.fsf@gitster.g> (raw)
In-Reply-To: <f3814646-4763-62e1-b64e-d1aab3fdbbc8@iee.email> (Philip Oakley's message of "Sun, 22 May 2022 23:02:43 +0100")
Philip Oakley <philipoakley@iee.email> writes:
> 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?
next prev parent reply other threads:[~2022-05-22 23:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 18:41 Git commands version documentation Hrushikesh Rao
2022-05-22 22:02 ` Philip Oakley
2022-05-22 23:35 ` Junio C Hamano [this message]
2022-05-23 11:10 ` Philip Oakley
2022-05-23 13:08 ` Ævar Arnfjörð Bjarmason
2022-05-23 15:19 ` Philip Oakley
2022-05-23 18:01 ` Ævar Arnfjörð Bjarmason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqr14l87jp.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=hrushikesh20thegreat@gmail.com \
--cc=philipoakley@iee.email \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.