(not) using loggo in github.com/juju/errgo

[Nate Finch]

I just noticed that errgo uses loggo for one single debug statement.  I
think this is a mistake if we want errgo to be reusable by the community.
 We should strive to make our independent packages actually independent....
removing unnecessary dependencies is a big part of that.  We shouldn't
force people to include loggo in their product if all they want is
errgo.... especially given that we're barely using loggo in the package.

Can we remove the debug code, or use the stdlib's logging or something?  I
don't think we're getting a lot of value out of using loggo in this package.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140520/3ca861b1/attachment.html>