Re: Making working copy sparse loses local deletes / moves
On Thu, Jun 16, 2016 at 11:32 PM, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
> Hi all,
> I'm following through on a thread I started on the users list, about
> "sparsifying a working copy"  (i.e. invoking 'svn up --set-depth
> empty' on a parent directory, in order to selectively retrieve
> specific children later). It looks like there is a bug when "emptying"
> a directory like that, and I'd like to get some opinions here about
> the expected behaviour.
> When making a directory depth=empty, svn is careful not to lose local
> modifications (modified files are left there as part of the sparse
> working copy -- same for added files). However, local deletes are lost
> (and consequently also moves are broken, only the A+ is left). It
> think that's a bug, it makes it hard to confidently make a working
> copy more sparse.
Filed an issue:
Received on 2016-06-20 22:59:51 CEST
This is an archived mail posted to the Subversion Dev