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

RE: Get exclusive lock

From: Reedick, Andrew <jr9445_at_ATT.COM>
Date: Tue, 4 Mar 2008 16:55:36 -0600

> -----Original Message-----
> From: Les Mikesell [mailto:lesmikesell_at_gmail.com]
> Sent: Tuesday, March 04, 2008 12:15 PM
> To: Reedick, Andrew
> Cc: users_at_subversion.tigris.org
> Subject: Re: Get exclusive lock
>
>
> Remind me here... how did the person who created the file know to set
> the needs-lock status in the first place? What if you create a
similar
> file? How will you know to set the property? If you have people who
> don't understand which files can have changes merged easily and which
> can't, you will not only have people who don't observe the needs-lock
> property, you aren't likely to have it set on the files that need it
> anyway - unless the people who edit files don't create new ones.

Meh, that's a problem with all version control systems when dealing with
unmergable files.

Either train the users, or have the admin pick up the slack.
Subversion's config file can go a long way to automatically flagging
files as 'svn:needs-lock' however, it's a pain to push the config file
to the clients. (I would really like a client side hook to update
peoples' config files.)

> Being
> 'mergable' or not is really an inherent property of the file type, not
> something dictated by the VC so you probably want to get a lock any
> time
> you plan to touch such files whether anyone else remembered to set the
> property in the VC or not.
 

True, but in such a case, the lock is useless, where useless == not
guaranteed:
        1) I checkout the file on Monday,
        2) you lock the file on Tuesday, and
        3) I try to check-in on Wednesday...
        4) I break your lock because I'll be damned if I'm going wait
for you to finish, and then re-do two day's worth of work.

Unless svn:needs-lock is there from the start, there's no guarantee that
someone else isn't already working on the file, and there's no guarantee
he'll ever find out about your lock until it's too late.

On the plus side, I think we finally have a case where DRM would be a
good idea... ;-)

*****

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. GA623

---------------------------------------------------------------------
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 23:56:18 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.