You can save a personal version of an object for your use.
Checkpointing an object preserves it in a state that is not modifiable,
but that you can delete later when you no longer need it. You must
own the object to perform a checkpoint. To checkpoint
an object, it must be in the working state.
About this task
ccm ckpt|checkpoint [-task task_spec] [-t|-to version|file_spec]
[-c|-comment comment_string] [-ce|-commentedit]
[-cf|-commentfile file_path] [-cr|-commentreplace] file_spec...
- -c|-comment comment
- Specifies to append a comment on all baseline projects and their
members when they are checked in to the released state.
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 that the contents of the specified file is used 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
is replaced with any existing comment.
- file_spec
- Specifies the file, directory, or project to checkpoint. See File specification for details.
- -p|-project
- Shows the history of a project.
- project_spec
- Specifies the project to list. See Project specification for more information.
- -t|-to version|file_spec
- Specifies the version and changes the name of the new, non-project
object, or specify the version of a new project or project hierarchy.
- -task task_spec
- Specifies the task with which you want your newly checked-out
object to be associated. See Task specification for details.
If you do not specify a task but a current task is
set, the newly created object version is associated with the current
task. Any task associated with the checkpoint object version remains
unchanged.
Example
- Checkpoint the current working version
of foo.c, and add a comment.
ccm
ckpt -c "Phase 1 works." foo.c
Adding 'release'
attribute with value '2.0' to object foo.c-3:csrc:11
Associated object foo.c-3:csrc:11 with task 36
Checkpointed object version: 'foo.c-2:csrc:11'
- Checkpoint the current working version of foo.c.
Add a comment and specify the new working object
version to be joe.
ccm
ckpt -c "Trying Joe's algorithm." -t joe foo.c
Adding 'release' attribute with value '2.0'
to object foo.c-joe:csrc:11
Associated object foo.c-joe:csrc:11
with task 36.
Checkpointed object version: 'foo.c-3:csrc:11'