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

Re: Locking issues

From: D.J. Heap <dj_at_shadyvale.net>
Date: 2005-04-13 15:59:24 CEST

Peter N. Lundblad wrote:
[snip]
>
> Regarding a conflicted file, you should have to grab a new lock to resolve
> a conflict. If you don't have a lock, the file should be read-only to
> remind you about that. Maybe I'm missing something from your explanation
> here?
>

Hmm, yes, I got the conflict after I had locked and updated the
out-of-date file. I did have the lock so the file should have been
editable, I think; however, I shouldn't have been able to get the lock
until I had already updated, so probably this is not a real issue once
the other issue of locking an out-of-date file is fixed.

Thanks!

DJ

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 13 16:04:26 2005

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

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