Re: please check your spam folders

2015-03-27 Thread James Tunnicliffe
Lots of CI emails end up in spam for me unless I specifically tell gmail not to. You can do this by creating a filter and ticking the never send to spam box, so for internal lists you could trust them. People in your contacts are trusted more than those who aren't for spam filtering purposes, but

Re: backporting changes to packages that use gopkg.in

2015-03-27 Thread Eric Snow
On Thu, Mar 26, 2015 at 7:53 PM, Nate Finch nate.fi...@canonical.com wrote: tl;dr: godeps overrides gopkg.in, so you can have godeps pin a commit from a different branch than gopkg.in is retrieving (i.e. make a release-number branch, like 1.22 and use godeps to pin commits from there, even if

Migrating imports away from code.google.com/p to golang.org/x

2015-03-27 Thread Nate Finch
Just an FYI: As you've probably heard, code.google.com is going away. It'll be read-only for a year IIRC and then *poof*. Most of the packages from the go authors lived there (crypto, etc), but now will be maintained at golang.org/x. We'll be changing our imports to point at the new repos, so

Re: Migrating imports away from code.google.com/p to golang.org/x

2015-03-27 Thread Eric Snow
On Fri, Mar 27, 2015 at 9:59 AM, Nate Finch nate.fi...@canonical.com wrote: Just an FYI: As you've probably heard, code.google.com is going away. It'll be read-only for a year IIRC and then poof. Most of the packages from the go authors lived there (crypto, etc), but now will be maintained

Re: backporting changes to packages that use gopkg.in

2015-03-27 Thread John Meinel
So it doesn't seem terrible for something that is just a copyright fix. *but* Having go get give you something very different than what we build with is just going to bite us in the future. John =:- On Mar 27, 2015 7:08 PM, Eric Snow eric.s...@canonical.com wrote: On Thu, Mar 26, 2015 at 7:53