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

RE: [TSVN] subversion and locks

From: Malte Bögershausen <mb_at_bbtsoftware.ch>
Date: 2005-09-19 01:06:08 CEST

> From: Simon Large [mailto:simon@skirridsystems.co.uk]
> Sent: Monday, September 19, 2005 12:21 AM
>
> Malte Bögershausen wrote:
> > We are using locks, but it ist quite hard to notice if a file
> > is locked by another user. If I'm not mistaken, with TSVN, the
> > only way to see is a file is locked by another user is in the
> > repo browser and with check for modifications.
> >
> > When there are many locks in the repository 'check for modification'
> > becomes hard to overview.
> >
> > I often only notice that someone else has locked a file that I
> > modified when trying to commit the change.
>
> The most effective way to use locking is to use the svn:needs-lock
> property as well. That way, files are read-only (and have a different
> overlay) *unless* you hold a lock for that file. The work
> flow is then:
> 1. Get lock
> 2. Modify file
> 3. Commit (releases lock automatically)

Thanks a lot for the quick reply.
Yes, I'm aware of the svn:needs-lock property.

At the moment this process is quite easy to ignore/forget with
MS Visual Studio. Visual Studio does not warn if you start to
edit an readonly file. Only if you try to save the changes a
dialog warns about it, but with an option to ignore the readonly
flag. So even when svn:needs-lock is set it's very convenient
not to lock (but that's clearly not a problem of TSVN).

>
> If you don't use svn:needs-lock, then locking is almost
> useless because
> it fails to stop 2 people working on the same file.

We are doing a lot of developemnt with VS.NET and the winforms designer.
As the generated code from the designer is hard (almost impossible) to
merge, a developer whos adds controls etc. normally locks the file.
But for other, smaller changes in the code we generally don't lock the files
as they are normally easy to merge.

So to demand a lock even for small modifications would mean a lot of
unnecessary locks, but still locks are needed for bigger, hard to merge
changes.

This will probably become much better with VS 2005 and partial classes,
when the written and generated code is in separate files.

Malte

>
> Simon
>
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.tigris.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Sep 19 01:06:27 2005

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