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

Re: Post commit script examples?

From: Greg Alexander <greg_at_alexanderzone.com>
Date: Thu, 19 Aug 2010 11:24:00 -0600

Hi Csaba,
     Thanks for the response. Yes, I am beginning to have a good feel for
what Subversion was designed for, but I would still like to implement
something. I saw the page in the book you reference, but I cannot find any
examples on how to really implement. Any pointers anyone can provide would
be great!

     Thanks,
     Greg

On Thu, 19 Aug 2010 18:39:56 +0200, Csaba Raduly <rcsaba_at_gmail.com> wrote:
> Hi Greg,
>
> On Thu, Aug 19, 2010 at 5:28 PM, Greg Alexander wrote:
>>
>> Hello,
>>    What I am
>> looking to do is to setup a way so that all files in the repository
>> require
>> a lock to be owned by the user before it can be committed the next
time.
>> I
>> also want this to be an automatically set property on any new files. I
>> have
>> users used TortiseSVN, some SVN program for Mac (really not sure), and
a
>> few accessing the repository command line. Trying to distribute
something
>> to all of them may or may not be adopted and we really need this to be
a
>> hard and fast rule. We have a situation today where we have many files
>> and
>> many editors of that code and we have people stepping all over each
>> other.
>
> It seems to me that you are trying to force Subversion to do something
> it was not designed to do. Subversion does not use the
> Lock-Modify-Unlock model but rather the Copy-Modify-Merge model (which
> it inherits from CVS). See section "Versioning Models" in chapter 1,
> Fundamental Concepts, in the svn book. (svnbook.red-bean.com)
>
> Having said that, it does support locking, at least on per-file basis.
> See section "Locking" in chapter 3, Advanced Topics.
>
>> What I would really like is a way to have SVN set a lock as soon as a
>> working copy is created, but I don't think that can be done. To me some
>> sort of autolocking solution would be ideal as then it would be clear
who
>> was working in what.
>
> That would prevent everybody from modifying anything, except the first
> person who created a working copy.
>
> --
> Life is complex, with real and imaginary parts.
> "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus
> Torvalds
> "People disagree with me. I just ignore them." -- Linus Torvalds
Received on 2010-08-19 19:24:41 CEST

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.