Suspend & Resume Perforce Changelists
Make a local sandbox right from P4V or P4Win |
||
It's how you wish Perforce changelists worked...
| The Problem | Standard Perforce Changelists | CodePickle + Perforce |
|---|---|---|
| A file can be a member of only one changelist at a time. | What happens when the same file is involved in two different changes? You cannot represent this in Perforce. | Because you can suspend changelists that aren't in use, you can add a file to another changelist. By switching between these changelists in CodePickle you can accurately represent the fact that the file is being modified in two different changelists. |
| File modifications in one changelist affect all the others. | You cannot "focus on" one changelist in particular. If you have broken code in one changelist, you cannot work on another one because the broken code is still there. | CodePickle lets you remove changelists from your active workspace. You can bring them back any time you want. |
Handle interruptions and context-switch between different programming
tasks with CodePickle and Perforce.
Get the benefits of local sandboxes with zero server load,
no heavy-weight branches, and no modification to the Perforce server.
