Justin Erenkrantz wrote:
>>
>> - svn cleanup --repair, a new flag
>> - svn cleanup, could be made to do it unconditionally
>> - svn status --repair, a new flag
>> - svn repair, a new function
>
> I think 'svn cleanup' should do it unconditionally. -- justin
I was hoping there would be a better (more automatic and invisible) way than
any of these four options, like making read-only operations (status, etc.) do
the fix-up as and when they notice the discrepancy. In fact, I think it was
discussed way back that they could attempt to convert their read lock to a
write lock on discovering the problem, and repair it if the write lock was
obtained, else leave it for another time.
But of these four options, I agree that "svn cleanup" is the best, because I
really don't want to see any new commands or options for a "feature" that
shouldn't need to exist (from a high-level-logic point of view). It is just
the sort of clean-up that the "cleanup" command is intuitively meant to
perform, so a "--repair" flag or "repair" command would be superfluous and
ambiguous. "status --repair" is illogical because the problem is not
specifically related to "status", though it may be most noticeable in "status".
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 22 22:06:21 2004