[p4] Workspace option: exclusive open

[Gabor Maghera]

I think we are on the same page as far as workspace or client definitions,
let's call it the client workspace as Perforce does, perhaps.

And you are correct, in order to integrate you do need a workspace which
encompasses the branch and the parent codeline.  Using dedicated workspace
for each codeline is a best practice for doing development work in that
codeline other then integrating.  That's a recommendation to be given to
developers who do work sometimes "here" and sometimes "there" as far as
codelines go.

Have a good weekend all,
Gabor

On 9/14/07, Ivey, William <william_ivey at bmc.com> wrote:
>
> If you're workspace can only see one branch, how do you integrate
>
> between release branches? (I can't see this being a best practice if
>
> it doesn't work - and, by the way, I got the idea from Perforce's own
>
> documentation.)
>
>
>
> If I have two workspaces and change directories, but forget to change
>
> workspaces (and P4CONFIG doesn't work with the GUI) then I might
>
> not submit a file into the wrong branch - but I will create a useless
>
> change on the wrong branch, and fail to update the branch I intended.
>
>
>
> Whereas if I have one workspace that maps multiple server branches
>
> to multiple directories on my system, changing directories is all I need
>
> to do and everything will go as intended. Perforce automatically directs
>
> the command to the right branch based on my local directory path no
>
> matter what client I happen to use. That's part of its design and I
> don't
>
> see any easy way to create the problem you describe by doing it this
>
> way.
>
>
>
> I think you are misinterpreting the term "workspace" (replace it with
>
> "client" and maybe my meaning will be clearer). I'm certainly not
>
> talking about mixing file from multiple branches in a single directory
>
> on my system.
>
>
>
> -Wm
>
>
>
>
>
> ________________________________
>
> From: Gabor Maghera [mailto:gmaghera at gmail.com]
> Sent: Friday, September 14, 2007 3:35 PM
> To: Ivey, William
> Cc: Rick Macdonald; perforce-user at perforce.com
> Subject: Re: [p4] Workspace option: exclusive open
>
>
>
> It may not be as efficient to set up a dedicated workspace for each
> codeline, but it is a safety guard and a best practice.  This is
> especially important for release codelines but it also helps with
> development codelines.  The idea is to reduce the likelihood of someone
> checking code into an inappropriate branch and therefore destabilizing
> it.
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>