On Wed, Jun 13, 2012 at 6:20 AM, Justin Case <send_lotsa_spam_h...@yahoo.com > wrote:
> ----- Original Message ----- > > > From: Ulrich Eckhardt <ulrich.eckha...@dominolaser.com> > > > > Sorry, but I'm afraid I didn't get across what I wanted to say. > > Correct. Let me simplify again my test case: > 1. I run svn update > 2. svn update finds a file in use, aborts > 3. I free the file, oops it seems I have to cleanup > > Why should I have to cleanup??? > svn update (see point 2) KNEW the file is in use, so instead of leaving > locks around it could just have skipped that file and print a message that > not everything have been updated. > JC > To detect a "locked file" as a safe change to reject and fail on, wouldn't Subversion have to know quite a bit about the underlying filesystem? This can be surprisiingly difficult, and is partly why lock files exist, to abstract that subtle knowledge into a more tangible "no, we're not kidding, leave this alone while we're doing atomic operations" stage. I'm not saying it's infeasible, just potentially more comlicated than you may realize.
