[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Script to obliterate the most recent revision(s)

From: Mark Phippard <markphip_at_gmail.com>
Date: Sun, 25 Mar 2018 18:53:48 -0400

>> 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.

Received on 2018-03-26 00:53:58 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.