[p4] Workspace option: exclusive open

[Shawn Hladky]

> How many times have you seen a change submitted that
> contains files from more than one branch?
We implemented a branch-cross trigger to prevent this.  And it fails a lot
of changelists.
Maybe our dev team is just more careless than average :-)

On 9/17/07, Ivey, William <william_ivey at bmc.com> wrote:
>
> > Showing your branched product as a single directory tree
> > isn't any more or less "real" than considering individual
> > branches separately. Your branching strategy is real enough.
>
> It's more real in the sense that it matches what the user
> sees through Windows Explorer, for example. They get testy
> if they go from there to P4Win and it looks like directories
> are missing.
>
> > How many times have you seen a change submitted that
> > contains files from more than one branch?
>
> None that I can recall, except where actually intended.
>
> -Wm
>
>
> -----Original Message-----
> From: Chuck Karish [mailto:chuck.karish at gmail.com]
> Sent: Sunday, September 16, 2007 5:07 PM
> To: Ivey, William
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] Workspace option: exclusive open
>
> On 9/16/07, Ivey, William <william_ivey at bmc.com> wrote:
> > Therefore, forcing Perforce to mask this reality seems
> counterproductive
> > and prone to errors
>
> Showing your branched product as a single directory tree isn't any
> more or less "real" than considering individual branches separately.
> Your branching strategy is real enough.
>
> > In five years, I've never seen a file submitted to the wrong branch I
> > attribute
>
> How many times have you seen a change submitted that contains
> files from more than one branch?
>
> There isn't any one right way to do this.  What makes sense to your
> users is best.
>
> --
> Chuck Karish   karish at well.com   (415) 317-0182
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>