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
Dnia 2016-10-12, o godz. 23:18:24
Thomas Modeneis napisał(a):
> 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.
And npm is happy to pull in multiple versions of the same library for
the same appl
Do you happen to use godep? I think I've had it cause this problem before.
On Thu, 13 Oct 2016 at 03:00 Tong Sun wrote:
>
> On Wed, Oct 12, 2016 at 5:56 PM, Thomas Modeneis wrote:
>
> The main problem seems to be related to go get believe me or not.
>
>
> I kind of agree, in the sense that what
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 the team/developer in charge
> 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 the team/developer in charge for the module, and the
module version is consequently bumped after.
So develo
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"?
> >
>
> The problem occ
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 provided no changes wer
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 do
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" mean it's
pulling and/or upd
> What would you suggest 'go get' can do to "do better"?
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.
On Thursday, October 13, 2016 at 7:31:37 AM UTC+2, Jan Mercl wrote:
>
> On Thu, Oct 13, 2016 a
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 received this message becaus
On Wed, Oct 12, 2016 at 5:56 PM, Thomas Modeneis wrote:
> The main problem seems to be related to go get believe me or not.
>
I kind of agree, in the sense that what we did, was purely "go get", and
never tempered with the git underneath. You can blame git, but I think "go
get" can do better to a
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 > napis
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 is a root cause of update f
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 (regardless of
version).
> @
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:
http://st
16 matches
Mail list logo