On Wed, Oct 19, 2011 at 1:08 PM, Hyrum K Wright <hyrum.wri...@wandisco.com> wrote:
> In following this discussion, I'd like to point out that while this > seems like an interesting problem, it doesn't feel like a showstopper > for 1.7.1. In other words, I'd like to ship 1.7.1 with our existing > high-impact fixes, rather than wait for this issue to be solved (which > may take some time, iiuc). 1.7.2 doesn't have to be too far away, and > you can problem ship patched binaries with your SharpSvn or Subclipse > releases. > > If I don't quite understand the gravity of this issue, please enlighten me. :) No, I agree with that. -- Thanks Mark Phippard http://markphip.blogspot.com/
