On Mon, Mar 26, 2018 at 12:53 AM, Mark Phippard <markp...@gmail.com> wrote: > >>> I'm concerned that users (admins) won't downdate all wc's ... >> >> During the Aachen hackathon we brainstormed a bit about obliterate, >> and figured it would be wonderful if a client, acting on a working >> copy, could detect that "history has been changed". Even if only to >> give an fatal error message "your working copy is broken, please check >> out a new one". >> >> So, how to detect that a working copy and the repository have a >> different idea of history, so we can error out loudly and clearly? >> >> Can it be done with current svn features? > > Assuming a repository admin is concerned about this, wouldn't they just use > svnadmin setuuid to give the repository a new UUID? Technically that is what > that is for and would immediately accomplish this goal. >
Yes, but that breaks *all* working copies, whether they are affected by the changed history or not. What would be vastly better, I think, would be that only "working copies containing traces of the changed history" would be broken. Thus salvaging "working copies with only non-affected subtrees" and "working copies at an older working revision". Especially in the case where you're obliterating the most recent revision(s) only, that could be a big deal. -- Johan
