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

From: Jim Barry <jim_at_chez-jim.net>
Date: Thu, 7 Jul 2016 10:36:19 +0000 (UTC)

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.

- Jim
Received on 2016-07-07 12:36:40 CEST

This message: [ Message body ]
Next message: Branko Čibej: "Re: "svn update --set-depth=exclude" exits prematurely, leaving repo in need of cleanup"
Previous message: Kristian: "AddressSanitizer: global-buffer-overflow message"
In reply to: Branko Čibej: "Re: "svn update --set-depth=exclude" exits prematurely, leaving repo in need of cleanup"
Next in thread: Branko Čibej: "Re: "svn update --set-depth=exclude" exits prematurely, leaving repo in need of cleanup"
Reply: Branko Čibej: "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 ]