Re: [go-nuts] Re: go get: You are not currently on a branch

2016-10-13 Thread Konstantin Khomoutov
On Thu, 13 Oct 2016 04:36:27 -0700 (PDT) Thomas Modeneis wrote: > > Does "NPM installs the target module" mean it's pulling and/or > > updating > its sources to a VCS? > > NPM decided that releases are part of a module. This module should be > release explicitly by

Re: [go-nuts] Re: go get: You are not currently on a branch

2016-10-13 Thread Konstantin Khomoutov
On Thu, 13 Oct 2016 07:15:56 -0400 Tong Sun wrote: > > > You can blame git, but I think "go get" can do better to avoid the > > problem in the first place. > > > > 'go get' just executes `git clone` or `git pull`. What would you > > suggest 'go get' can do to "do better"? >

Re: [go-nuts] Re: go get: You are not currently on a branch

2016-10-13 Thread Jan Mercl
On Thu, Oct 13, 2016 at 1:15 PM Tong Sun wrote: > The problem occurs between two consequent 'go get' that may have a long time span. If > > git checkout master > > is suppose to fix the problem, then 'go get' should at least try to do that, I suppose. It fixes the problem

Re: [go-nuts] Re: go get: You are not currently on a branch

2016-10-13 Thread Tong Sun
On Thu, Oct 13, 2016 at 1:31 AM, Jan Mercl wrote: > On Thu, Oct 13, 2016 at 3:59 AM Tong Sun wrote: > > > You can blame git, but I think "go get" can do better to avoid the > problem in the first place. > > 'go get' just executes `git clone` or `git pull`. What would you suggest > 'go get' can

Re: [go-nuts] Re: go get: You are not currently on a branch

2016-10-13 Thread Jan Mercl
On Thu, Oct 13, 2016 at 8:18 AM Thomas Modeneis wrote: > I hate comparing Go with Node, but (I'm sorry)... How about doing the same that NPM does ? NPM installs the target module + target version. End. I'm not familiar with Node. Does "NPM installs the target module"

Re: [go-nuts] Re: go get: You are not currently on a branch

2016-10-12 Thread Jan Mercl
On Thu, Oct 13, 2016 at 3:59 AM Tong Sun wrote: > You can blame git, but I think "go get" can do better to avoid the problem in the first place. 'go get' just executes `git clone` or `git pull`. What would you suggest 'go get' can do to "do better"? -- -j -- You

Re: [go-nuts] Re: go get: You are not currently on a branch

2016-10-12 Thread Thomas Modeneis
Hi Oir, The main problem seems to be related to go get believe me or not. I manage to get this right after I deleted $GOPATH/pkg/* and $GOPATH/src/golang.org Thanks On Wednesday, October 12, 2016 at 3:51:07 PM UTC+2, ohir wrote: > > Dnia 2016-10-12, o godz. 02:37:16 > Thomas Modeneis

Re: [go-nuts] Re: go get: You are not currently on a branch

2016-10-12 Thread Wojciech S. Czarnecki
Dnia 2016-10-12, o godz. 02:37:16 Thomas Modeneis napisał(a): > You are not currently on a branch. Please specify which > branch you want to merge with. See git-pull(1) for details. This is common to freshmen to get a checkout of some tag then forget they did it. This

Re: [go-nuts] Re: go get: You are not currently on a branch

2016-10-12 Thread Jan Mercl
On Wed, Oct 12, 2016 at 2:27 PM Thomas Modeneis wrote: > Oh this is one of the problems that is really time consuming. I'm not sure if this is related, but I've never had this kind of problems before +1.7. Not being on a git branch is quite probably not caused by Go

Re: [go-nuts] Re: go get: You are not currently on a branch

2016-10-12 Thread andrey mirtchovski
this is more of a git problem, not a go problem. you're in a 'detached head' state and don't have a current branch to consider as your base. the best remediation is to issue 'git checkout master' in the respective repository. that will provide a correct head to work with. for more info: