Branko Čibej wrote: > Bert Huijben wrote: >> Changing the recorded timestamps would require obtaining a write lock while >> performing a status walk... which is a breaking change for any client that >> wants to do things concurrently. -1 on 'just doing it' There is a good reason >> the current code only updates timestamps when it has a write lock. Otherwise >> it would break concurrent operations. >
> I absolutely agree. 'svn status' has never write-locked the working > copy. There are clients out there that rely on this documented fact. > One of them is TortoiseSVN. I don't dispute that, but there seems to be an assumption there that if it takes out a lock on this metadata then that lock will necessarily have to be "the [present] WC write lock" which will therefore block operations such as 'update'. Is it inconceivable that some different level, granularity or kind of locking strategy could be used? - Julian
