On 7/1/06, Marvin D. Toll <MarvinToll@gtcgroup.com> wrote:
> Subversion supports locking through its 'svn lock'/'svn unlock' commands.
>
> [MDT] The *key* word of my inquiry was "force". I understand the default
> implementation of Subversion (for example as implemented by SourceForge) to
> support "optional" locking - however, my world is not one in which such
> options are bestowed to commodity developers - onshore or offshore.
> [...]
> [MDT] The "Harry" example leaves it to the individual developer to make a
> decision often made corporate-wide at large companies. Excerpt:
>
> "An example is in order, to demonstrate. Let's say that Harry has decided to
> change a JPEG image. To prevent other people from committing changes to the
> file, he locks the file in the repository using the svn lock command ..."
To force developers to lock files, use the svn:needs-lock property.
This property is usually intended to be used on files which cannot be
merged automatically (e.g. JPEG files).
http://svnbook.red-bean.com/nightly/en/svn.advanced.locking.html#svn.advanced.locking.lock-communication
Cheers,
David
--
David James -- http://www.cs.toronto.edu/~james
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 1 18:32:09 2006