On 5 March 2014 20:14, Gustavo Niemeyer wrote:
> On Wed, Mar 5, 2014 at 5:12 PM, Nate Finch 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 li
On Wed, Mar 5, 2014 at 5:12 PM, Nate Finch 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 idea to do
> it on pur
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 se
If you used juju/go-log-v1, you might import this as
gonuts.org/juju/v1/log, which is rather neat, and would properly
version the API.
On Wed, Mar 5, 2014 at 5:03 PM, Tim Penhey wrote:
> Hi all,
>
> I'm just preparing a branch that will change the loggo imports from
> github.com/loggo/log
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 loggo
