file lock. When the file has a lock, other users know the file is being edited, and you can
avoid merge issues.To enforce locking files, modify entries in the SVN config file. To locate your SVN
config file, see “Register Binary Files with SVN” on page 32-18.(^1) To make files with a .m extension read only, add a property to your SVN config file
in the [auto-props] section. If there is no entry for files with a .m extension, add
one with the needs-lock property.
.m = svn:needs-lock=yes
If an entry exists, you can combine properties in any order, but multiple entries must
be on a single line separated by semicolons.
(^2) To make files with a .mlx extension read only, add a property to your SVN config
file in the [auto-props] section. Since you must register files with a .mlx
extension as binary, there is an entry for the file type. Add the needs-lock property
to the entry in any order, but on the same line and separated by a semicolon.
.mlx = svn:mime-type=application/octet-stream;svn:needs-lock=yes
(^3) Re-create the sandbox for the configuration to take effect.
With this setting, you need to select Get File Lock before you can edit files with a .m
extension. See “Get SVN File Locks” on page 32-29.
Share a Subversion Repository
You can specify a repository location using the file:// protocol. However, Subversion
documentation strongly recommends that only a single user access a repository directly
via file:// URLs. See the Web page:
http://svnbook.red-bean.com/en/1.7/svn-book.html#svn.serverconfig.choosing.recommendations
CautionDo not allow multiple users to access a repository directly via file:// URLs or
you risk corrupting the repository. Use file:// URLs only for single-user repositories.
Be aware of this caution if you use MATLAB to create a repository. MATLAB uses the
file:// protocol. Creating new repositories is provided for local, single-user access only,
for testing and debugging. Accessing a repository via file:// URLs is slower than using
a server.
32 Source Control Interface