Re: Git log of all (modifying) commands run on a repo?

Linus Torvalds [off-list ref] writes:

On Wed, 7 Feb 2007, Bill Lear wrote:

quoted

I thought that it would be very useful to have a history of git
commands that have been run against a repo, in order to hopefully
debug this sort of thing --- perhaps only those that modify the repo.

The "reflog" is kind of that, and you can literally do

	less .git/logs/refs/heads/master

to get some kind of idea what's up.

Newer gits enable reflogs by default, older gits don't (and *really* old 
git versions don't support it at all).

Of course, we should probably just have a

	git reflog show

command for this to make it prettier.

	$ git log -g?

Junio C Hamano [off-list ref] wrote:

	$ git log -g?

	[git (build)]$ git log -g?
	fatal: unrecognized argument: -g?

I think its:

	[git (build)]$ git log -g ?
	commit 6506e156d99bd406661cd5d2e502db7c0960d716
	Reflog: HEAD@{0} (Shawn O. Pearce [off-list ref])
	Reflog message: merge origin/master: Fast forward
	Author: Junio C Hamano [off-list ref]
	...

at least with bash.  :-)

-- 
Shawn.

On Wed, 7 Feb 2007, Junio C Hamano wrote:

quoted

Of course, we should probably just have a

	git reflog show

command for this to make it prettier.

	$ git log -g?

You think that is *prettier*?

No, I think that if I want a log, I'll just do the "less", thank you very 
much ;)

		Linus