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

Re: Question about svn:externals linking within a repository

From: Jason Harrison <harrison_at_koolhausgames.com>
Date: Tue, 11 Mar 2008 10:07:38 -0700

Andy Levy wrote:
> On Tue, Mar 11, 2008 at 5:23 AM, Simon Large
> <simon.tortoisesvn_at_googlemail.com> wrote:
>
>> On 11/03/2008, Jason Harrison <harrison_at_koolhausgames.com> wrote:
>>
>> > - Is my repository setup somewhat rational or totally screwy? Before I arrived here we didn't have a Trunk or Tags or Branches. All of the folders were right at the root, and people would check out the five or so that they needed to work with. Morning updates would grab way too much data.
>>
>> It works, but why bother with the externals? Just have artists
>> checkout svn://repository/project/_Trunk/Art
>> and engineers checkout svn://repository/project/_Trunk.
>>
>
> Maybe in combination with directory permissions, so that the artists
> don't "accidentally" check out more than they need?
>
> Couldn't you just set /project/_Trunk/Code to "Artists = " (can't see
> the directory at all), and then tell everyone to check out
> /project/_Trunk ?
>
We have Artists, Designers, Producers, Engineers, and Testers. Each
role has a potentially different set of folders to checkout, commit to
and work from. Hopefully there will be little confusion!

Andy, I don't understand your suggest to set "Artists =" -- is this a
property, a permission?

-Jason

Jason Harrison
Video Game Software Engineer
Koolhaus Games Inc.
206 - 896 Cambie Street
Vancouver, B.C. V6B 2P6
Studio Tel: 604 696 9797
Mobile Tel: 604 644 8611
www.koolhausgames.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-03-11 17:07:59 CET

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.