[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: Feature request: Warning on get lock

From: Jody Shumaker <jody.shumaker_at_gmail.com>
Date: 2006-04-28 22:43:30 CEST

On 4/28/06, Edward Harvey <eharvey@chilsemi.com> wrote:
> So I just want to be clear on this --
>
> Basically, everyone is saying (Jody, Sven, Simon, Hans-Emil, Lubbe)
>
> If you don't want someone else to work on a file, presumably because you
> are going to work on it extensively, you must first manually set the
> needs-lock property. You must then manually commit. You must then
> manually obtain lock.
>

We don't agree with your process, why would we care about automation of it?

When locking I don't care if someone else wants to work on a file, all
I care about is that I can insure no one can modify the file in
source-control till I'm done.

Then on the flip side, all I care is to know if someone possibly
locked a file I'm currently working on or will be working on. In my
company this is so rare I never bother to check as the act of checking
would take more time then its worth overall. If you're in a company
where locking is frequent, then it could pay off to either repeatedly
check if someone has locked something, or setup a post-lock hook that
e-mails all concerned about new locks.

Subversion works perfectly fine for both sides. I don't see any reason
to use the horribly complicated set of steps you described and see the
svn:needs-lock only useful for when it is a unmerge-able file.

Sometimes trying to force a program into what you see as the ideal use
is foolish. Instead you should focus on how you can properly use it
to get what you want. You've repeatedly not commented on the whole
issue with the fact your proposed method still has a huge flaw in that
other uses will have to do updates on a very frequent basis, and that
if they instead just used the check for modifications dialog like I've
repeatedly mentioned they could get the same thing without your
complex set of steps.

- Jody

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Apr 28 22:43:39 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.