Checkpointing a project

You can save a personal version of a project for your use only. Checkpointing a project preserves it in a state that is not modifiable, but you can delete it later when you no longer need it. The name of the state is checkpoint. You must own the project to perform a checkpoint. To checkpoint a project, it must be in the working state. However, a project cannot be checkpointed if any of its members (files, directories, and sub projects) are in the working state. After the project is checked into the checkpoint state, the system creates another version of the project in the working state.

About this task

ccm ckpt|checkpoint -p|-project [-t|-to version] 
        [-c|-comment comment_string] [-ce|-commentedit] 
        [-cf|-commentfile file_path] [-cr|-commentreplace] project_spec...
-c|-comment comment
Specifies to append a comment on each project. The comment can contain more than one line and accepts backslash encoded values.
You can use this option with -commentedit and -commentfile. If you use the -commentedit option, the comment displays in the default text editor.
-ce|-commentedit
Specifies to start the default text editor to compose and edit the comment. The result saved from the text editor is used as the final comment. You can use this option with the -comment and -commentfile options.
-cf|-commentfile file_path
Specifies to use the contents of the specified file for the comment. If you specified -comment, it is appended to that comment. You can use this option with the -commentedit option.
-cr|-commentreplace
Normally, the comment specified is appended to any existing comment. However, if you use the -cr option, the new comment replaces any existing comment.
-p|-project project_spec
Checkpoints a project. See Project specification for details.
-t|-to version
Sets the version of the newly checked-out project.

Feedback