[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Communication of LOCKS and CHANGES

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: 2007-11-20 17:03:34 CET

Erik Huelsmann wrote:

>> Then I can take action or postpone my work.
>> Right now, I don't see that it is locked until I try
>> to commit it or I _remember_ to explicitly check for locks.
> If a file can't be merged, this is where your error is: your workflow
> conflicts with the type of file you're chaning. You need to lock the
> file before editing it. No need to check for locks: 'svn lock' will
> tell you someone else has the file locked already, all this means
> you're doing *more* work than required, not less. If you were to lock
> the files before editing them, instead of "update", "status", "lock",
> "update", you could do with "lock", "update". Clearly this is less
> work.

Yes, what matters is nearly always whether you can _get_ a lock, not
whether someone else has recently had one, and since this is an atomic
operation, the only way to know is to do it.

   Les Mikesell
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 20 17:04:15 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.