Re: "svn update --set-depth=exclude" exits prematurely, leaving repo in need of cleanup

From: Branko Čibej <brane_at_apache.org>
Date: Thu, 7 Jul 2016 13:12:59 +0200

On 07.07.2016 12:36, Jim Barry wrote:
> Branko Čibej writes:
>> I can reproduce this with 1.9.4 and trunk ... definitely a bug, only
>> dir/subdir2 should be left (since dir/subdir2 is unversioned content of
>> dir).
> Thanks Brane. Would it be possible for an svn dev to take this on?
>
> By the way, I just checked it with 1.8.16 and everything works as
> expected, so it seems this bug was introduced in 1.9.x.

Please file a bug with the reproduction script.

-- Brane
Received on 2016-07-07 13:10:57 CEST

This message: [ Message body ]
Next message: Jim Barry: "Re: "svn update --set-depth=exclude" exits prematurely, leaving repo in need of cleanup"
Previous message: Jim Barry: "Re: "svn update --set-depth=exclude" exits prematurely, leaving repo in need of cleanup"
In reply to: Jim Barry: "Re: "svn update --set-depth=exclude" exits prematurely, leaving repo in need of cleanup"
Next in thread: Jim Barry: "Re: "svn update --set-depth=exclude" exits prematurely, leaving repo in need of cleanup"
Reply: Jim Barry: "Re: "svn update --set-depth=exclude" exits prematurely, leaving repo in need of cleanup"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]