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

Re: Roadmap for 1.1

From: Simon Raess <cocoa_at_gmx.ch>
Date: 2004-04-02 17:47:30 CEST

Am 01.04.2004 um 23:14 schrieb Walter Nicholls:

> 1. Locking
> Well, you're dealing with that. Note that the lockingplan.txt when I
> read seemed to focus on Exclusive locks only - we need shared/advisory
> locks as well (and locks must have the user recorded against them or
> the
> advice is not so useful)

Aren't advisory locks all that's needed. Exclusive locks may work when
the users are all working at the same location but it does not work
when developers are situated all over the world (as usual in opensource
projects). Even if users are all at the same location there exist some
problems. Imagine what happens if somebody locks a file and leaves for
holidays... (I know, there are admin commands)

I imagine something like edit/unedit (or lock/unlock or ...). Before I
use a file that should be locked (specified by a svn property?), I call

$ svn edit myfile.txt

If somebody else is already editing the file I get a message that tells
me who is editing the file. I can then talk with this person (maybe he
has forgotten to release the lock...). If I'm really sure what I'm
doing I could specify a command line option that overrides the warning

Let's say I'm the first person who wants to edit that file. After my
work is completed, I simple type

$ svn unedit myfile.txt

and the lock is released.

Isn't that all that's needed? If not, please enlighten me ;-)


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 2 17:47:16 2004

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.