I don't quite understand the rush each time to break backwards
compatibility. I guess Go doesn't let you have compile time flags, so if
you want to use any new functionality there's no good way to do it
optionally.
Anyway, as long as 1.2 gets backported to Precise and Saucy we could do so.
I certai
On Sun, Apr 27, 2014 at 8:19 AM, Martin Packman
wrote:
> I've poked utils/ssh a bit during gophercon.
>
> Unfortuately the update to use tip of go.crypto can't land right now
> as it requires a couple of standard library crypto bits that go 1.1.2
> lacks. Perhaps we can talk about bumping the requ
I've poked utils/ssh a bit during gophercon.
Unfortuately the update to use tip of go.crypto can't land right now
as it requires a couple of standard library crypto bits that go 1.1.2
lacks. Perhaps we can talk about bumping the requirement for building
trunk juju-core to go 1.2 and adding that in
