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

Re: Subversion 1.2, files needing locks, and commit

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-05-16 13:47:35 CEST

On Mon, 16 May 2005, Dave Proctor wrote:

> I've been waiting for version 1.2 for a while now, and tried it for the
> first time over the weekend. It looks very good - I've just got a question:
> It seems that if I have a file which has the svn:needs-lock property set,
> but currently noone has taken the lock, if I alter my working copy of that
> file, and then just do a svn commit, the file will be submitted into the
> repository. Is this correct? I've tried when another user does have the
> lock, and again the commit tries to upload the changed file, but fails with
> the fact the other user has the lock.
You can use a pre-lock hook script to disallow that. The design is

> The reason I ask is that currently we use a system where you have to lock
> then modify, and submit changes. We've got into the habit of being able to
> make temporary changes to files with no risk of them being uploaded to the
> latest version.

So, ideally, you'd want it to ignore modified files with svn:needs-lock
and that are not locked? If so, no, that's not possible. But you can
reject the commit and remind people to undo their local changes.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 16 13:40:44 2005

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.