User Guide - MKS

Resync CP
Backfill List
Using the Resync CP Command
For example, consider a simplified application in the main trunk of
development for the Aurora project (Aurora_Project.pj). The project
member, tool.c, includes a bug fix for Issue 24 and is associated with the
file tool.c (revision 1.7) through change package (CP) 24:1.
The developer wants to pick up the changes that address the bug fix and
apply these in a sandbox. In the developer’s sandbox, tool.c is at revision
1.2.
To apply the bug fix in the sandbox, the developer uses the si resynccp
command to apply CP 24:1 as follows:
si resynccp -S c:/Aurora_Project/project.pj 24:1
Applying change packages...
24:1
The following warnings have occurred:
-------------------
The change package(s)
20:1 -- tool.c(1.3)
21:1 -- tool.c(1.4)
22:1 -- tool.c(1.5)
23:1 -- tool.c(1.6)
are required in order to apply this list of change
packages. They will be automatically added to the list,
since the backfill option is set to Entire Change
Package(cp).
--------------------
*** The following set of operations will be performed:
Project: f:/Aurora_Project/project.pj
Sandbox: c:\Aurora_Sandbox\project.pj
Member tool.c: resynchronize to Revision 1.7
Are you sure you wish to proceed? [yn]: y
In this case, Resync CP updates the working file revision for tool.c from
1.2 to 1.7 in the sandbox. This is done by checking out tool.c at 1.7 into
the sandbox. The changes made from revisions 1.3 through 1.6 are already
included in this checked out file.
The following provides an example of the backfill list and how it works in
the Resync CP command. The main project, Aurora_Project.pj, now
includes an additional bug fix for project member, tool.c. Issue 23
addresses that bug fix and is associated with the file tool.c (revision 1.6)
through CP 23:1.
377