"Michael Mattox" <michael.mattox@verideon.com> writes:
> > > Also is there a work-a-round?
> >
> > You can always use properties, and a pre-commit step that rejects
> > commits to files which have "locked" property set.
>
> It's more complicated than that because I want to prevent people from
> modifying binary files which are "locked". At commit time it's too late,
> someone may have done an hour of changes on the file. I understand the
> developers of SVN are against file locking, but when a lot of users are
> requesting it, and even refusing to use SVN until it has locking, I really
> think it should be a higher priority.
This statement is an unfair characterization of Subversion developers.
I believe it is safe to say that, yes, we believe that concurrent
development models and high communication levels are crucial to the
success any collaborative development environment. But many (if not
all) of us also understand the benefits of a locking system -- that
such a system does sacrifice concurrency, but does so to enhance
communication.
Subversion *will have* support for some form of locking.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 22 15:54:14 2004