On Thu, Oct 13, 2016 at 7:35 AM, Konstantin Khomoutov wrote:
Sure, in 90% (or more) of bare (that is, "central") Git repos found in
> the wild, HEAD points at refs/heads/master, and that's why `git clone`
> creates a local branch "master" for you pointing to the same commit
> "origin/master" point at, but still the name "master" is not at all
> special when cloning. When someone told you to do `git checkout master`
> it was actually a conscious oversimplification to avoid explaining the
> stuff I have just explaining.
Then the problem should at least be made aware of to the lib authors / go
developers -- it is the go-sqlite3 <http://github.com/mattn/go-sqlite3> that
was causing me problems. I.e., it surprised me that even such popular
module's author doesn't know the "catch", and switched Git HEAD randomly.
> Changing the subject of this discussion a bit, I think that embedding
> more magic into `go get` is wrong...
OK. I can buy that.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.