list versions that need to be patched into the workspace’s version


accurev patchlist -v <from-ver-spec> [ -V <to-ver-spec> ] 
[ -t <transaction-range> ] [ -fx ] [ <element-list> | -e <eid> ]


The patchlist command compares two versions of each specified element: the “from” version specified with -v and the “to” version specified with -V. If you omit the -V option, the version in the current workspace is used; if you don’t specify any elements, all the elements in the “to” workspace/stream are considered.

If a transaction range is specified with -t, patchlist only considers the versions involved in those transactions for the comparison.

For each element, patchlist lists all the real versions that contain changes that are present in the “from” version, but have not yet been incorporated into the “to” version. If no elements are specified, all the elements in the “to” workspace/stream are considered.

For example, to find which of Allison’s versions of file brass.h contains changes that Derek has not yet incorporated:

accurev patchlist -v brass_dvt_allison -V brass_dvt_derek brass.h

Derek can then incorporate selected changes with one or more invocations of the patch command. If he wants to incorporate all of Allison’s changes, he might prefer to perform a single merge command, not a series of patch commands.

Note: An invocation of the patch command can, in effect, incorporate several versions’ changes into the target version. See the patch reference page for details.

patchlist merely provides information: the depot-relative pathname and version-ID of each version, along with the number of the keep transaction in which that version was created. For example:

\.\src\brass.h t:88 (5/23)
\.\src\brass.h t:87 (5/22)
\.\src\brass.h t:86 (5/21)
\.\src\brass.h t:85 (5/20)

patchlist does not perform any actual patch commands.


-v <from-ver-spec>

Specify the version which has the desired changes. You can use a version-ID (gizmo_dvt/5) or a stream (gizmo_dvt).

-V <to-ver-spec>

Specify the version that you wish the changes to be incorporated into. You can use a version-ID (gizmo_dvt/5) or a stream (gizmo_dvt).

-t <transaction-1-transaction-2>

A transaction range, used with the -v and -V options to compare the versions between the two listed transactions.

For the patchlist command, a transaction can be represented in the following ways:

Time keyword: now

Transaction number as a positive integer: e.g. 146 or 23965

Transaction number keyword: highest

-e <eid>

The element-ID of the element to be analyzed. If you use this option, you cannot also specify an <element-list>.


Display the results in XML format.


For all elements find the versions in the gizmo_dvt stream containing changes that have not yet been incorporated into the gizmo_test stream:

> accurev patchlist -v gizmo_dvt -V gizmo_test

See Also

merge, mergelist, patch

Using a Specific Version of an Element