[p4] Are remote depots any good for this scenario?

Chuck Karish chuck.karish at gmail.com
Tue Jul 4 15:24:04 PDT 2006


On 7/3/06, Wade Scholine <Wade.Scholine at citrix.com> wrote:
> We have multiple perforce servers in our organization. There is a server
> on which developers are allowed to create private sandbox branches. A
> developer who has since left the company started a project by syncing a
> workspace to a branch in one of the production depots, and then adding
> the files in the workspace to his sandbox. My colleague has taken over
> the project and will soon have to merge the changes from the sandbox
> back into the production depot. We are trying to find a way to retain
> the history from the sandbox.
>
> A brute-force approach to what we want would be to create a branch in
> the production depot corresponding to the initial state of the sandbox,
> sync that branch to the successive changes to the sandbox, opening the
> files that were changed in each, submit each change to the new branch in
> the production depot, and finally integrate the new branch into the
> current production branch.
>
> Would we be able to get the same result by creating a remote depot on
> the production server, pointed at the sandbox server?

Not all the metadata is served across remote mounts.  Try it and
see whether it serves your purpose.

> Or, alternatively, is there tool that would do what's described in the
> paragraph about the brute-force approach?

VCP

-- 
Chuck Karish   karish at well.com   (415) 317-0182



More information about the perforce-user mailing list