Re: 1.7.0-beta2 this afternoon

On Thu, Jul 21, 2011 at 06:44, Philip Martin <philip.martin_at_wandisco.com> wrote:
> Greg Stein <gstein_at_gmail.com> writes:
>...
>> Yup. It was listed as an issue for the 1.7.0 release. Now that it has
>> been fixed.. sure: it should be merged to 1.7.x, and we're good to go.
>
> Enable a whole bunch of new code, and then say "look no bug reported" :)

Not sure what you're asking for here. We had issue 3888 for fixing in
1.7.0. It has been fixed. I have tested the change *extensively*, and
am aware of no bugs at all in that code. We wanted the fix in 1.7.0,
so it ought to be merged.

Now... you're saying something separate below:

> The first thing I tried leaks memory:
> http://subversion.tigris.org/issues/show_bug.cgi?id=3967

Are you suggesting that my fix for 3888 caused this problem, or is
incorrect in some way? Or is this a new, distinct, and undiscovered
problem that you're bringing up?

Cheers,
-g
Received on 2011-07-21 13:56:36 CEST