Thread (4 messages) flat view 4 messages, 2 authors, 2016-06-15

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

From: Eugene Sajine <hidden>
Date: 2016-06-15 22:47:59

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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help