Re: git-log produces no output

From: Linus Torvalds <torvalds@osdl.org>
Date: Apr 21, 2006, 18:11 UTC
Message-ID: <Pine.LNX.4.64.0604211102000.3701@g5.osdl.org>
In-Reply-To: <20060421172001.44441.qmail@web60325.mail.yahoo.com>

On Fri, 21 Apr 2006, Bob Portmann wrote:

>
>  I cannot get any output out of it and am wondering if I am using it
> correctly or it is broken.

You're using it correctly, but it isn't broken for me.

> As I understand it, git-log should just print out the log messages but 
> not the changes, whereas git-whatchanged will print out both.

Well, in 1.3.0, "git log" can actually do both, and you can get the whatchanged output by just saying "git log -p".

But yes, without the "-p", you should get just the log.

And that's exactly what I get, both with current HEAD git, and with a v1.3.0 checkout.

Show 5 quoted lines

> test-log> git log
> test-log> 
> 
> As you can see git log produces no output.  I've tried it with other
> options with the same result.

Very strange indeed. Can you do

	git log > file

to see if that changes (and see if the file contains anything)? The reason I mention that is that by default "git log" will start a pager for you, and if you somehow have a broken PAGER setup, I could imagine exactly the behaviour you see (although I don't see why "git whatchanged" would work either, in that case).

Finally, if that doesn't output anything either, please do (for just that small repository, so that the trace is also small)

	strace -o git-trace git log > /dev/null

and send out the result. Again, for PAGER reasons, that "> /dev/null" is actually important, because we don't want to trigger the pager code.

		Linus