Upcoming import change for loggo

Hi all, I'm just preparing a branch that will change the loggo imports from github.com/loggo/loggo to github.com/juju/loggo I felt that it would be good to get a bunch of useful Go libraries under the juju banner, and I saw no reason not to put loggo there. If you are using

Re: Upcoming import change for loggo

For the record, I'm not a fan of duplicating the package name of anything in the standard library. Obviously, sometimes collisions will happen if a new package is added to the standard library, but it seems like a bad idea to do it on purpose. When you're deep in the middle of a file, and you

Re: Upcoming import change for loggo

On Wed, Mar 5, 2014 at 5:12 PM, Nate Finch nate.fi...@canonical.com wrote: For the record, I'm not a fan of duplicating the package name of anything in the standard library. Obviously, sometimes collisions will happen if a new package is added to the standard library, but it seems like a bad

Where should loggo live (and errgo, ...)?

Hi Currently, the loggo library used by juju-core is hosted on Github at github.com/loggo/loggo. Given juju-core is moving to github.com/juju, it's been proposed that loggo move across to github.com/juju/loggo. We already have github.com/juju/errgo. My question is this: when I see a project

Re: Where should loggo live (and errgo, ...)?

On 06/03/14 15:46, Ian Booth wrote: Hi Currently, the loggo library used by juju-core is hosted on Github at github.com/loggo/loggo. Given juju-core is moving to github.com/juju, it's been proposed that loggo move across to github.com/juju/loggo. We already have github.com/juju/errgo.