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

Re: Get lock bug?

From: Ryan Schmidt <subversion-2006d_at_ryandesign.com>
Date: 2006-11-16 20:47:52 CET

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
Received on Thu Nov 16 20:48:45 2006

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.