purge elements with changes that are already in the backing stream


accurev rebase [ -c <comment> ] [ -s <stream> ] [ -i ]


The rebase command purges elements in your default group according to specific criteria. When you perform a rebase operation, AccuRev purges elements from a stream or workspace when the current version of the element is:

  • the same as what is in the backing stream
  • underlapped with the backing stream
  • stranded

A rebase operation is useful when you want to allow inheritance, resolve underlaps, or purge stranded elements.

In some situations, such as when you change a stream basis time from some time in the past to something more current, there may be files in your default group for which inheritance is blocked. You can use the rebase command as a quick way to purge these files so that inheritance can take place.

Another scenario in which a rebase operation is useful is after you have reparented a stream in such a way as to create underlapped files. Rebasing the stream purges the underlapped files and resolves the underlapped state.

Note: Rebase is also an option of the purge command.


–c <comment>

Specify a comment for the transaction. The next command-line argument should be a quoted string. Alternatively, the next argument can be in the form @<comment-file>, which uses the contents of text-file <comment-file> as the comment.

-s <stream>

Stream to purge changes from. If you do not specify a stream, AccuRev rebases the workspace associated with your current directory location.

Note: Invoking rebase -s causes the depot’s pre-promote-trig trigger to fire.


Purge any stranded elements. Stranded elements are members of the default group that no longer have a pathname in the workspace or stream.


Rebase stream gizmo:

> accurev rebase -s gizmo

See Also