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

Re: Roadmap for 1.1 (locking)

From: C.A.T.Magic <c.a.t.magic_at_gmx.at>
Date: 2004-04-02 18:14:12 CEST

Jay Glanville wrote:

>>Simon Raess wrote:
>> >> 1. Locking
>> >> Well, you're dealing with that. Note that the
>>lockingplan.txt when I
>> >> read seemed to focus on Exclusive locks only - we need
>> >> locks as well (and locks must have the user recorded
>>against them or the
>> >> advice is not so useful)
>>I have a question on locking and svn in general:
>>when locking a single file, you would only lock
>>for example
>> /trunk/foo.txt
>>but all other branches that contain this file
>> /bar/Branch01/foo.txt
>> /bar/Branch02/foo.txt
>>would remain unlocked, since svn is unable
>>to detect that these are branches and are related.
>>Or do I misunderstand that?
> Correct. That is my common usage of locking in other SCM systems. The
> primary purpose of locking is to prevent collisions. Editing the same
> file in two different branches doesn't cause a collision.

but how will this work if the locking is intended to prevent collisions
between unmergable binary files?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 2 18:14:36 2004

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.