From: Philip Oakley <philipoakley@iee.email>
To: Hrushikesh Rao <hrushikesh20thegreat@gmail.com>, git@vger.kernel.org
Subject: Re: Git commands version documentation
Date: Sun, 22 May 2022 23:02:43 +0100 [thread overview]
Message-ID: <f3814646-4763-62e1-b64e-d1aab3fdbbc8@iee.email> (raw)
In-Reply-To: <ccb312dc-c2cc-ca3a-e659-0f87ceec0d15@gmail.com>
On 22/05/2022 19:41, Hrushikesh Rao wrote:
> Hey,
>
> I am working on git maintenance project in Jenkins. We are using
> git-maintenance to improve the performance of the git commands further
> improving the build speed. Git maintenance was added in git version
> 2.30.0. The aim of the project is to also support systems having git
> version < 2.30.0. Few git maintenance tasks very available before the
> maintenance command was introduced i.e gc,commit-graph,gc and
> incremental repack.
> Is there a way for me to find out in which version these commands have
> been introduced? Based on this we can support legacy git version.
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
--
Philip
next prev parent reply other threads:[~2022-05-22 22:03 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 [this message]
2022-05-22 23:35 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f3814646-4763-62e1-b64e-d1aab3fdbbc8@iee.email \
--to=philipoakley@iee.email \
--cc=git@vger.kernel.org \
--cc=hrushikesh20thegreat@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).