Karl Fogel wrote:
> Blair Zajac <blair_at_orcaware.com> writes:
>
>> Before I read the proposal, I was thinking you would want to run
>> obliterate which would create a new repository that one would examine
>> before making the new repository the master, so the original would not
>> be modified.
>>
>
> We could offer that as an option.
>
>
>> Also, how would it deal with commits happening using nodes that are
>> being obliterated?
>>
>
> The same way it deals with nodes that were already there. (I.e., think
> about it and you'll see there's no difference.)
>
>
>> Also, it seems changing the UUID of the new repository would be a good
>> idea to force clients to do a new checkout.
>>
>
> I think that could be an option, but not required: some people don't
> want any obvious trace that an obliterate ever happened.
>
With the almost-required fresh checkout, I don't think that's an option,
is it?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-17 13:42:39 CEST