Well, On 3 February 2016 at 20:41, Tianon Gravi <admwig...@gmail.com> wrote: > On 15 December 2015 at 13:32, Michael Hudson-Doyle > <michael.hud...@canonical.com> wrote: >> FWIW, this bug is fixed properly upstream in git tip and will be part of 1.6. > > Nice! :D > > The upstream fix applies cleanly against Go 1.5 -- do you think it's > important enough to include now, or just wait for Go 1.6 to be GA > (which will be soon anyways)?
TBH, I'm a bit vague about what problems exactly this bug actually caused (even though I spent half a week fixing it!). So I guess that's a shrug from me -- if it's not causing active problems and 1.6 is, as you say, around the corner, I'd just as soon leave it out. Cheers, mwh
