You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Bilokon, Paul " <pa...@citi.com> on 2010/05/18 08:40:44 UTC

Assertion Failures in tree_conflicts.c

Hi,

We have recently encountered the behaviour described in this Issue:

http://subversion.tigris.org/issues/show_bug.cgi?id=3469

The issue is currently listed as "NEW", but looks like it was opened in August 2009.

Are there any plans to address it in forthcoming releases or perhaps it has been fixed already?

Best wishes,
Paul

Paul Bilokon, Vice President
Citigroup | FX - Options Trading | Quants
33 Canada Square | Canary Wharf | Floor 3
London, E14 5LB
Phone: +44 20 798-62191
paul.bilokon@citi.com<bl...@citi.com>

RE: Assertion Failures in tree_conflicts.c

Posted by "Bilokon, Paul " <pa...@citi.com>.
Many thanks, Stefan!

Best wishes,
Paul

-----Original Message-----
From: Stefan Sperling [mailto:stsp@elego.de]
Sent: 18 May 2010 16:52
To: Bilokon, Paul [ICG-MKTS]
Cc: 'users@subversion.apache.org'; Moudry, Jiri George [ICG-MKTS]
Subject: Re: Assertion Failures in tree_conflicts.c

On Tue, May 18, 2010 at 09:40:44AM +0100, Bilokon, Paul  wrote:
> Hi,
>
> We have recently encountered the behaviour described in this Issue:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=3469
>
> The issue is currently listed as "NEW", but looks like it was opened in August 2009.
>
> Are there any plans to address it in forthcoming releases or perhaps it has been fixed already?

I've committed a fix, it is now pending review for inclusion in 1.6.12.
I've updated the issue accordingly.

Thanks for prodding,
Stefan

Re: Assertion Failures in tree_conflicts.c

Posted by Stefan Sperling <st...@elego.de>.
On Tue, May 18, 2010 at 09:40:44AM +0100, Bilokon, Paul  wrote:
> Hi,
> 
> We have recently encountered the behaviour described in this Issue:
> 
> http://subversion.tigris.org/issues/show_bug.cgi?id=3469
> 
> The issue is currently listed as "NEW", but looks like it was opened in August 2009.
> 
> Are there any plans to address it in forthcoming releases or perhaps it has been fixed already?

I've committed a fix, it is now pending review for inclusion in 1.6.12.
I've updated the issue accordingly.

Thanks for prodding,
Stefan