From: Jeff Hostetler <git@jeffhostetler.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
balaji marisetti <balajimarisetti@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git command history
Date: Fri, 22 Mar 2019 09:19:36 -0400 [thread overview]
Message-ID: <f52ef736-9d58-a6cf-e3b0-501b065ae325@jeffhostetler.com> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1903221343090.41@tvgsbejvaqbjf.bet>
On 3/22/2019 8:46 AM, Johannes Schindelin wrote:
> Hi Balaji,
>
> On Tue, 19 Mar 2019, balaji marisetti wrote:
>
>> Can anyone please tell me if there is way to see the command history
>> of a local git repo?
>
> If you really are only interested in the *Git* commands, you will be able
> to implement something on top of the Trace2 feature (which just made it
> into `master` but not into any official Git version yet, so it will most
> likely be available when Git v2.22.0 comes out).
>
Trace2 will let you see all of the git commands,
the alias expansions, and any shell commands launched
by git. If those shell commands also run git commands,
they will be listed too.
However, it can't tell you what was otherwise done within
the shell script.
> If you are instead interested in all shell commands in a local Git
> worktree (you probably meant the worktree, not the repository, I assume),
> then you might need to play some games with Bash aliases to override `cd`
> and reroute the history by re-setting `HISTFILE` and then calling `history
> -cr` or something similar.
>
>> If there isn't a way, why hasn't the command-history feature been
>> implemented?
>
> Because Git is an open source project. This means that nobody is
> responsible for fulfilling your wishes, except for you. And you can do it,
> too, this project welcomes all high-quality contributions.
>
> Ciao,
> Johannes
>
next prev parent reply other threads:[~2019-03-22 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 16:03 git command history balaji marisetti
2019-03-20 0:47 ` Junio C Hamano
2019-03-22 12:46 ` Johannes Schindelin
2019-03-22 13:19 ` Jeff Hostetler [this message]
2019-03-25 15:40 ` balaji marisetti
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=f52ef736-9d58-a6cf-e3b0-501b065ae325@jeffhostetler.com \
--to=git@jeffhostetler.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=balajimarisetti@gmail.com \
--cc=git@vger.kernel.org \
/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 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 NNTP newsgroup(s).