From: Eugene Sajine <euguess@gmail.com>
To: Thomas Rast <trast@student.ethz.ch>, git@vger.kernel.org
Cc: Eugene Sajine <euguess@gmail.com>
Subject: Re: origin/branchname and tracking branch pointing to different commits?
Date: Thu, 7 Jan 2010 18:50:10 -0500 [thread overview]
Message-ID: <76c5b8581001071550g31e9f5a3n15ebdb10a806ab2e@mail.gmail.com> (raw)
In-Reply-To: <76c5b8581001070925g21ac3136x2928f12dc43437e5@mail.gmail.com>
>
> 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
next prev parent reply other threads:[~2010-01-07 23:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-07 17:03 origin/branchname and tracking branch pointing to different commits? Eugene Sajine
2010-01-07 17:06 ` Matthieu Moy
2010-01-07 17:12 ` Thomas Rast
2010-01-07 17:25 ` Eugene Sajine
2010-01-07 23:50 ` Eugene Sajine [this message]
2010-01-08 0:32 ` Junio C Hamano
2010-06-08 16:27 ` Eugene Sajine
2010-06-08 17:25 ` Junio C Hamano
2010-06-08 17:50 ` Eugene Sajine
2010-06-08 18:30 ` Jeff King
2010-06-28 17:43 ` Eugene Sajine
2010-06-29 19:27 ` Junio C Hamano
2010-06-29 20:05 ` Eugene Sajine
2010-06-29 22:39 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=76c5b8581001071550g31e9f5a3n15ebdb10a806ab2e@mail.gmail.com \
--to=euguess@gmail.com \
--cc=git@vger.kernel.org \
--cc=trast@student.ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).