RE: Read-only files?

This post will get you started on the pre-commit script:
http://svn.haxx.se/users/archive-2005-12/0596.shtml

Lieven.

> -----Original Message-----
> From: Gavin Lambert [mailto:gavinl@compacsort.com]
> Sent: maandag 19 december 2005 23:03
> To: 'Bruce Webber'
> Cc: users@subversion.tigris.org
> Subject: RE: Read-only files?
>
> Quoth Bruce Webber <mailto:brucewebber@fastmail.us>:
> >> This is true, but if no one else has acquired a lock, there is
> >> nothing that prevents me from making the file writable and then
> >> committing it. The locking isn't strongly enforced by the
> system in a
> >> way that prevents me from editing the file unless I lock it. The
> >> problem arise when I start to edit the file without
> locking it, and
> >> then someone else locks the file before I commit.
> >
> > I agree. Subversion's locking mechanism is driven from the client
> > rather than the server, which allows for the problem you describe.
>
> The precommit hook script is probably the way to go then.
> I'm sure you'll be able to get svnlook to tell you whether a
> user has locked a file or not.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.371 / Virus Database: 267.14.1/206 - Release
> Date: 16/12/2005
>
>

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.1/206 - Release Date: 16/12/2005
 
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org