[p4] Sandboxes without branching
fabien.ninoles at gmail.com
Fri Aug 24 08:03:33 PDT 2007
I have to do something similar because of our checking policy in the
mainline (all checkins must be revised and carefully test, which can slow
things down a lot). So, I used a Private Version instead by using Mercurial
on top of my client. Mercurial have some really nice feature for queuing
change and is designed from the ground up to be used with an external
revision tree (the DSCM model relied on this).
This post (
do something similar except I didn't use tailor since I don't care about
keeping my private history in the server. hg just allow me to have the
flexibility of a DSCM for my work, while still following the company policy
for the mainline.
Hope this help,
2007/8/23, Mark Lee <mlee at minitab.com>:
> For the sake of argument, let's say that user branches cannot be
> created. Users want to edit a group of files for some time in a sandbox
> with complete (though temporary) version history and then submit into
> Perforce. How would one then create such a sandbox?
> Several recent threads have mentioned various shelving methods (p4tar,
> scripts, etc.) and a third-party product, CodePickle. These solutions
> all seem to involve a save/rollback/resume model that does not include
> support for versioning. One solution I'm investigating involves using
> both a local and remote Perforce server with separate workspaces mapped
> to the same root. Obviously this would require user diligence to keep
> each up to date but in theory this looks like it should work.
> Has anyone else worked on a similar system or have any ideas how best to
> accomplish this?
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user