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

Re: Branching a locked project

From: Simon Large <simon.tortoisesvn_at_gmail.com>
Date: Thu, 23 Aug 2012 15:26:48 +0100

On 23 August 2012 15:12, Gerald Britton <gerald.britton_at_gmail.com> wrote:
> I used the Tortoise SVN "Get Lock" command to lock a project that I want to use as a template for others (so that only I or another admin can update it). I committed the change then, to test it, branched it to create a new project.
> I was surprised to find that the files in the new project all had the read-only property set. Since commits to the new project would not affect the template (though a merge-reintegrate would, of course), I had thought that the new branch would begin life on its own -- unlocked!
> Is this working as expected?

Presumably you set the svn:needs-lock property, which is what causes
the read-only status. When you copy a project you also copy its

So yes, you're right a new branch does start life unlocked, and
because you don't hold a lock you get a read-only copy. You have to
Get Lock in order to make it writeable. Or you need to remove the
svn:needs-lock property from those files.


:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-08-23 16:26:53 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.