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

RE: Get lock is not visible to other users

From: Gerasimov, Ivan <Ivan.Gerasimov_at_transas.com>
Date: 2006-04-26 16:57:11 CEST

I would Hello, Hans-Emil!

 

> > Problem:
> > 1- Set the file as "Get Lock"
> > 2- File appear as locked in my folder.
> > 3- Other user run "update" , but the file appears as "no lock"
> > 4- User change the file without a problem
> > 5- User try to commit and receive a erro with information that the file is locked by someonelese..

>

> This is not a bug.

>

> See the FAQ: http://tortoisesvn.sourceforge.net/node/163 <http://tortoisesvn.sourceforge.net/node/163>

>

> This is a question that appears fairly regularly on the mailinglist.

>

> I would suggest that a warning is displayed if a user tries to lock a file that lacks the "svn:needs-lock"-property, as this seems to confuse a lot of > users and is sort of pointless.

 

I would vote against such a warning. We store binary databases in svn repository. Therefore they cannot be merged and one must obtain lock each time before modifying and committing. The problem is that those databases cannot be even _viewed_, if they have readonly attribute set. Database engine just refuses to deal with such files. The database format isn't ours, so we can't change the behavior.

 

A warning on each locking would be very annoying.

 

>

> The warning could either be a part of the lock-dialog or a popup window (ick), and should preferably contain information about the svn:needs-> lock property.

 

Sincerely yours,

Ivan Gerasimov
Received on Wed Apr 26 16:57:33 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.