[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Differences in tree conflict reporting between 1.8 and 1.9 (possible regression?)

From: Stefan Sperling <stsp_at_elego.de>
Date: Thu, 9 Apr 2015 17:59:50 +0200

On Thu, Apr 09, 2015 at 05:49:19PM +0200, Marc Strapetz wrote:
> For a working copy which has been checked out using SVN 1.8, "svn info"
> output is slightly different between version 1.8 and 1.9 -- for 1.9 the
> local *dir* is missing.
>
> For 1.8:
>
> $ svn info a/b
> Path: a\b
> Name: b
> Repository Root: ...
> Repository UUID: ...
> Node Kind: none
> Schedule: normal
> Tree conflict: local *dir* missing, incoming dir edit upon merge
> Source left: (dir) ^/trunk/a/b_at_1
> Source right: (dir) ^/branch/a/b_at_4
>
> For 1.9:
>
> $ svn info a/b
> Path: a\b
> Name: b
> Repository Root: ...
> Repository UUID: ...
> Node Kind: none
> Schedule: normal
> Tree conflict: local missing or deleted or moved away, incoming dir edit
> upon merge
> Source left: (dir) ^/trunk/a/b_at_1
> Source right: (dir) ^/branch/a/b_at_4
>
> In terms of JavaHL this means that for version 1.8:
>
> info.conflicts[0].nodeKind="dir"
>
> while for version 1.9:
>
> info.conflicts[0].nodeKind="none"
>
> I can provide a test repository to reproduce this difference.
>
> -Marc

The 1.8 implementation was confused because there are sometimes mulitple
'kinds' involved in tree conflicts because there are multiple sides
with different kinds.

The kind shown is the local kind. 1.8 was wrong.
Received on 2015-04-09 18:00:42 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.