Menu
Is there a way to create a bundle of files with perforce so that it is in a "held" state, not checked in, so that it can be retrieved easily?
972
The p4 clean command takes the following actions when finding inconsistencies between files in a user's workspace and corresponding depot files: Files present in the workspace, but missing from the depot are deleted from the workspace. Files present in the depot, but missing from your workspace.
If you are in workspace browsing mode, the tree displays all the files in your workspace, including those not managed by Perforce. (You'll recognize the Perforce-managed files by their icons.)
p4 add opens files within the client workspace for addition to the depot. The specified files are linked to a changelist. The command can add files to a new, empty depot or to a depot that already contains files. The files are added to the depot when the changelist is committed with p4 submit .
Perforce allows you to check out the head revision or any previous revision of a file. To enforce the IDEs' check-in and check-out procedures, Perforce controls the read-write permissions of files. When files are checked out for edit, their permissions are set to read-write.
It sounds like the "shelve" functionality might be what you're looking for. The documentation is here. Basically it keeps the files on the server, but they're not actually submitted. You (or others) can then "unshelve" the changes into your clientspec.
If your server version (2009.2 or earlier) doesn't support shelving, you might also want to check out p4tar, which can package a changelist into a file that can later be restored to your workspace.
134
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
