>
> I don't follow your train of thought.
>
> The maxim "don't lose any user data" is indeed one we live by, but we
> apply the maxim to situations where the data might be lost *without*
> the user expecting it to happen. For example:
>
> * when receiving a conflicting update, create all three fulltexts
>
> * don't allow the deletion of something that's out-of-date
>
> * don't ever overwrite an unversioned file
>
> But is this situation, you're objecting to the safety of a command
> who's *purpose* in life is to toss changes! It's like objecting to
> the unix 'rm' command -- "but doctor, it might delete data!" -- "then
> don't do that."
But rm has -i.
That's all I'm proposing.
Cheers,
Karl P
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Aug 10 07:17:24 2003