You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Carlos Alberto Leme Galassi <ga...@cpqd.com.br> on 2006/11/16 17:31:45 UTC
Get lock bug?
Hi all!
When I set the 'svn:needs lock' property on a binary file, I force a person before change it, get the write permission through 'get lock' operation.
Then, when I did it, in my file subversion properties, I see the fields 'lock owner' and 'lock creation date' filled with the right information, but in other machines the persons couldn't see who is locking the file for changes - these fields appear empty.
Is it the correct behavior?
I´m using server 1.3 and client 1.4.0-7501.
Thanks
Carlos Galassi
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Get lock bug?
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Nov 16, 2006, at 11:31, Carlos Alberto Leme Galassi wrote:
> When I set the 'svn:needs lock' property on a binary file, I force
> a person before change it, get the write permission through 'get
> lock' operation.
>
> Then, when I did it, in my file subversion properties, I see the
> fields 'lock owner' and 'lock creation date' filled with the right
> information, but in other machines the persons couldn't see who is
> locking the file for changes - these fields appear empty.
>
> Is it the correct behavior?
Yes; the book says so:
http://svnbook.red-bean.com/nightly/en/
svn.advanced.locking.html#svn.advanced.locking.discovery
"Sally is left wondering who made the lock, when, and why. Once
again, svn info has the answers:"
[snip]
"If the main argument to svn info is a working copy path, then all of
the working copy's cached information is displayed; any mention of a
lock means that the working copy is holding a lock token (if a file
is locked by another user or in another working copy, svn info on a
working copy path will show no lock information at all). If the main
argument to svn info is a URL, then the information reflects the
latest version of an object in the repository; any mention of a lock
describes the current lock on the object."
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Get lock bug?
Posted by Tim Hill <dr...@comcast.net>.
How did the other person check the lock status? They need to get this
from the server, not the working copy.
--Tim
On Nov 16, 2006, at 9:31 AM, Carlos Alberto Leme Galassi wrote:
> Hi all!
>
> When I set the 'svn:needs lock' property on a binary file, I force
> a person before change it, get the write permission through 'get
> lock' operation.
>
> Then, when I did it, in my file subversion properties, I see the
> fields 'lock owner' and 'lock creation date' filled with the right
> information, but in other machines the persons couldn't see who is
> locking the file for changes - these fields appear empty.
>
> Is it the correct behavior?
>
> I´m using server 1.3 and client 1.4.0-7501.
>
> Thanks
>
> Carlos Galassi
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org