On Thu, Oct 30, 2014 at 10:34 PM, 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?
> Naturally master on origin should be match upstream, which may require
> you to pull-upstream-push-origin.
Why naturally? I don't use "master" in my fork of juju, I just use
feature/bug branches.
The "master" branch in my repo tracks upstream/master.
For local clones in my $GOPATH
> where I'm not doing development (i.e. ones created by go get), I don't
> have upstream set and origin still points to github (or wherever). So
> the behavior of go get works fine for me.
>
> As to making godeps honor the "upstream" remote, the focus for godeps
> should be on what's in each official repo. The revisions in our
> dependencies.tsv should be coming only from there. If it's
> conventional to use "upstream" for those official remotes (it *is* our
> recommended convention in {juju}/CONTRIBUTING), then it would be nice
> for godeps to try it first. The alternative is that folks be more
> diligent about making sure their "origin" clones are up-to-date with
> upstream, which is sometimes easy to do before running godeps.
>
> -eric
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
