as per: https://groups.google.com/d/msg/golang-nuts/3GtbT2s2HCc/djHr2YXFzEQJ

--

I do not think "goinstall -u" does what its author intended. It does this:

git fetch
git show-ref release
git checkout release

"git fetch" does not alter "release". It alters
"origin/release" (along with other branches, on all remotes: "man
git-remote"). You need to follow-up with

git merge FETCH_HEAD

to do a true update, assuming that the branch is actually tracking something. For
details:

http://www.kernel.org/pub/software/scm/git/docs/git-fetch.html
http://git.661346.n2.nabble.com/FETCH-HEAD-question-td2339060.html

But merging can me a mess. I have a better idea:

git fetch origin  # to avoid wasting time on other remotes
git show-ref origin/release
git checkout origin/release

"origin" is ok, since goinstall implicitly created the remote with that name
when it cloned the repo. You would then see

$ git branch
* (no branch)
  master
  release

"(no branch)" is explained here:
http://edspencer.net/2009/10/git-what-to-do-if-you-commit-to-no-branch.html
Generally, you never commit to "no branch". The "origin/release"
thing is a pseudo-branch, technically a "remote tracking branch". You cannot
alter its head; it just tracks the remote when you "fetch". No merging is
necessary.

The other benefit is that I can change which remote "origin" refers to, as I
just described in another post.

goinstall -v github.com/blah/blah/blah
cd gopath-dir/src/github.com/blah/blah/blah
git remote rename origin official  # official/release is the official branch now.
git remote add origin git://~me/path
git fetch origin
git branch --set-upstream release origin/release
goinstall -v -u github.com/blah/blah/blah

At that point, "-u" will fetch from my own github repo. (And currently, it
will change me to the "release" branch, but fail to merge from
"origin/release". I hope that's clear.)
Report abusePost reply