On 30 October 2014 14:34, Eric Snow <eric.s...@canonical.com> wrote: > On Thu, Oct 30, 2014 at 4:40 AM, roger peppe <roger.pe...@canonical.com> > wrote: >> It's a pity then that if you "go get" a package, origin is the repo >> you've branched from. There is always one of those, but you >> don't necessary have a fork of the repo yourself. > > Why wouldn't you want go get to fetch from your clone by default?
What Andrew said. Also, the only information that "go get" has when a repository doesn't exist locally is the home of that repository. So when "go get" gets a new package, the only place that origin can point to is that repository's home. When starting work on a package, the first thing I will do is invariably "go get" that package, which will fetch all new dependencies too. For the majority of those dependencies, I won't already have forked them on github. If I come to start work on one of those dependencies, it will already have an "origin" remote pointing to the source of the repo. So it's much easier IMHO just to go with the flow and keep origin always meaning the same thing, whether you've forked the repo or not. FWIW I never use "git clone" to copy Go package repositories locally. -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
