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

RE: RE: RE: RE: Re: Get exclusive lock

From: Reedick, Andrew <jr9445_at_ATT.COM>
Date: Tue, 4 Mar 2008 09:09:32 -0600

> -----Original Message-----
> From: Nick.Thompson_at_infineon.com [mailto:Nick.Thompson_at_infineon.com]
> Sent: Tuesday, March 04, 2008 8:58 AM
> To: users_at_subversion.tigris.org
> Subject: RE: RE: RE: Re: Get exclusive lock
> I don't understand how this helps. If I've just spent all day air
> brushing somebody out of a photo, how will being told by Tortoise,
> that I've wasted my time a few seconds or minutes after I save it help
> me? If nobody else has the lock or had the lock, I might get away with
> it, but if another users has got/had the lock and spent all day adding
> a
> UFO in to the background or adding horns and a tail to the person I've
> just air brushed out, this feature gains me little. I will find out as
> soon as I try to commit anyway.
> I really need the painting tool to warn me the file is read only/not
> locked by me before I start. Or maybe wrap the tools in a checking
> script that warns the user before starting the tool. This way I should
> be reminded to get the lock and not waste my time editing.

Some of us hit 'alt-f-s' (file save) unconsciously after every minor
change and would benefit from such a feature before too much time was
wasted. =)

A Windows box running the Server service can use 'net file' to see who
has locks on files, if the file is opened over a network share. In
theory, you could share your workspace, map a drive to the share, and
have a script run 'net file' and check for 'svn:needs-lock'. Any apps
would need to access the workspace via the mapped drive or file locks
won't be detected. Putting your subversion workspaces below a
long/silly dir name would help reinforce the need to use the mapped
drive instead.

Or you could get in the habit of automatically saving a file before you
start working on it in order to establish readonly status and/or to give
the 'svn:needs-lock' warning script a chance to work.

Real Solutions would be a Subversion aware painting tool, a painting
tool that respects read-only files property (pops up a message when you
make the first edit,) or something like ClearCase dynamic views which
intercept file I/O calls. However, even something as uber as a
ClearCase dynamic view won't help you from wasting hours on a file if
the painting app doesn't actually warn you that the file is readonly
when you make the first edit in memory.


The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA621

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-04 16:34:06 CET

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.