On Mon, Nov 8, 2010 at 8:29 AM, Jakub Narebski <jnareb@xxxxxxxxx> wrote: > Martin von Zweigbergk <martin.von.zweigbergk@xxxxxxxxx> writes: >> On Mon, Nov 8, 2010 at 4:02 AM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote: >>> Vitaliy Semochkin wrote: >>> >>>> I cloned a remote repository >>>> to check recent changes in origin/master I do: >>>> git fetch origin master > > This fetches into FETCH_HEAD _only_ from "origin" *remote*. > >>>> git log origin master > > This show log of 'origin/HEAD', which probably is 'origin/master'... > but which didn't get updated, and local branch 'master'. > >>>> >>>> recently I found out that log doesn't show recent commits >>> >>> Yes, this can be confusing. >> >> I agree and I believe this has come up a lot of times before. I talked >> to Jeff and Junio about this at GitTogether and Jeff said he has a patch >> for it that he would try to get up to date in a while. (Thanks, Jeff!) > > How can this issue be solved? The meaning of parameters in 'git fetch' > is different from meaning of parameters in 'git log'. > Sorry, maybe I misunderstood what the confusion was about. What I was referring to was the confusion caused by 'git fetch origin master' not updating 'refs/remotes/origin/master'. /Martin -- To unsubscribe from this list: 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