--- Linus Torvalds <torvalds@xxxxxxxx> wrote:
> 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.
>
> > 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).
Yes, this is the problem. It works when I send it to a file. It seems
to be that having any extra options my PAGER command that messes it up
(see below). If get-log was a shell script I would imagine that some
quotes are missing:-)
Bob
test-log> export PAGER='more'
test-log> git log
commit 9a4d7602fff052b6796c2862edddd11ae2e45d08
Author: Bob Portmann <portmann@removed>
Date: Fri Apr 21 10:56:11 2006 -0600
Two line hello
commit a38306518c5e5e8eb630c02a47bec2a9fc292025
Author: Bob Portmann <portmann@removed>
Date: Fri Apr 21 10:55:44 2006 -0600
One line hello
test-log> export PAGER='more -i'
test-log> git log
test-log>
Adding the option -i (which should do nothing) has eliminated the
output.
> 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
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html