git: 'log master..origin/master' not behaving as expected

Posted by steve jaffe on Stack Overflow See other posts from Stack Overflow or by steve jaffe
Published on 2010-03-18T21:36:11Z Indexed on 2010/03/18 21:41 UTC
Read the original article Hit count: 387

Filed under:

I'm trying to compare my copy of 'master' to that on the remote repository which it tracks. I thought that the following command would work, and often it seems to. However, sometimes it produces nothing and yet I know that the remote branch has many changes, which I can confirm by doing a pull.

git log master..origin/master

Can anyone explain this behavior and tell me what command I should be using to determine the changes between local and remote?

[Another piece of data: I've had it happen that 'git log master..origin/master' produces nothing. Then I do a pull. The pull fails because I have a working copy of some file. After this, 'git log master..origin/master' does show me the differences. It seems the pull has updated some local log? If so, how could I achieve this without doing (or attempting to do) a pull?]

© Stack Overflow or respective owner

Related posts about git