subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Branko ─îibej <br...@apache.org>
Subject Re: File and folder names corrupted when importing from CVS using cvs2svn
Date Wed, 24 Jan 2018 14:00:17 GMT
On 24.01.2018 14:11, Nico Kadel-Garcia wrote:
> On Thu, Jan 18, 2018 at 6:55 PM, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>> Andreas Krey wrote on Thu, 18 Jan 2018 19:14 +0100:
>>> svndumping, filtering and reloading may fix the file names for
>>> all revisions, but I have no idea how the client sandboxes
>>> will react to that.
>> The term is "working copies", and if when changing the history one should
>> 'svnadmin setuuid' the repository, which will cause all network
>> operations from old working copies to error out up front with a UUID
>> mismatch error message (as desired).
> This is also when you rename the upstream Subversion hostname or reset
> the URL for it altogether, so that old and broken working copies are
> reported as completely absent. It helps prevent people from doing an
> "svn switch" and expecting the histories to be consistent, and lets
> them know that the old repository is unusaable: a new working copy
> should be checked out.


Actually one cannot "svn switch" to a repository with a different UUID,
so changing that should be enough.

-- Brane


Mime
View raw message