[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: Bob Archer <Bob.Archer_at_amsi.com>
Date: Thu, 23 Aug 2012 16:57:07 -0400

> 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?

Why not use path passed authorization so the template path is read-only expect for admins?



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-08-23 22:57:16 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.