Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 13 Jun 2016 08:52:18 +0000
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Johan Corveleyn <jcorvel@gmail.com>
Cc: users@subversion.apache.org
Subject: Re: Is there a way to 'sparsify' a working copy, without starting
 over?
Message-ID: <20160613085218.GA3164@tarsus.local2>
References: <CAB84uBXwDpEpe+sjsZ36zdYU-iLhmwJiGVa7UD18=9WLz1pm=w@mail.gmail.com>
 <84bddb20-ce64-2da7-9121-068f31e7b569@apache.org>
 <CAB84uBXCEkigKwvJAJi+LFmRtWB8hmqCzOEetpfzt_8Q1em62w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAB84uBXCEkigKwvJAJi+LFmRtWB8hmqCzOEetpfzt_8Q1em62w@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
archived-at: Mon, 13 Jun 2016 08:52:25 -0000

Johan Corveleyn wrote on Mon, Jun 13, 2016 at 10:04:13 +0200:
> But if you have local moves, it seems the 'Delete' part of the move is
> lost when updating to depth empty, and the move is broken (converted
> into just the A+ of the "Add" part).
> 
> This looks like a bug in "update --set-depth" (losing information
> about local deletes (potentially part of a move)).
> Other than that, this technique seems to work fine.

Is the bug specific to --set-depth?  It sounds like a delete-delete tree
conflict, in which case, I would expect the following scenario to
trigger the same behaviour:

# greek tree
svnadmin create r
svn co -q file://$PWD/r wc
cd wc
touch iota
svn add -q iota
svn ci -q -m r1
svn up -q
# scenario:
svn rm -q -m r2 ^/iota
svn mv -q iota kappa
svn up

Sorry, I can't test this right now...

Daniel