[p4] File "Sharing"

[Dix, John]

We currently implement item 'A' listed below which works well for
everyone but we have a developer who found the same file listed twice in
two separate branches (he's the one who organized that section of the
branch) and he wanted to be lazy. :)

Thanks Steve.

-----Original Message-----
From: Stephen Vance [mailto:steve at vance.com] 
Sent: Thursday, April 03, 2008 3:28 PM
To: Dix, John
Cc: perforce-user at perforce.com
Subject: Re: [p4] File "Sharing"

File "sharing" the way VSS does it is a really bad error prone feature 
to make up for a poor branching model. It appears convenient to 
developers at the expense of reliability and accountability from an SCM 
perspective.

The Perforce equivalents that don't suffer these problems are a) 
branching the original to multiple locations and integrating when you 
choose to migrate changes around, or b) map the same region of your 
depot into your workspaces so everyone syncs off the same source.

The former lets projects choose when to deal with the changes by other 
projects. The latter avoids the overhead of the integrations but you 
lose the choice offered by the former.

Steve

Dix, John wrote:
> Hi all,
>
>  
>
> A developer asked if Perforce allows file "sharing" like VSS does.
This
> is where you can link a filea.cpp in BranchA with filea.cpp in
BranchB.
> They are the same file and if you make changes in BranchA, the changes
> are then propagated to BranchB. 
>
>  
>
> I have not heard of Perforce allowing this but thought I should ask.
>
>  
>
> Thanks...
>
>  
>
> -jdix
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>   

-- 
Stephen Vance
www.vance.com