Re: origin/branchname and tracking branch pointing to different commits?

From: Eugene Sajine <euguess@gmail.com>
Date: Jan 7, 2010, 23:50 UTC
Message-ID: <76c5b8581001071550g31e9f5a3n15ebdb10a806ab2e@mail.gmail.com>
In-Reply-To: <76c5b8581001070925g21ac3136x2928f12dc43437e5@mail.gmail.com>

Show 10 quoted lines

>
> Yep. That's what i though it is. I.e. origin/branchname will point
> always to the last pushed commit only. Isn't it a bit strange that git
> fetch doesn't update origin/qa?
>
> Probably the problem is that whenever I'm pulling or pushing to remote
> repo i expect the last updated state of particular remote branch to be
> reflected in origin/branchname, but IMHO it is correct expectation...
>
> What do you think?

let me correct my self a little bit:

$ git pull origin branchname

and

$git fetch origin branchname

are both causing the output like this:

>From git://....

* branch      branchname    -> FETCH_HEAD
...

but "git fetch" says:

>From git://....

* branch      branchname    -> origin/branchname

Is this inconsistent behavior necessary by design?

Thanks, Eugene