Table 8-5 summarizes the actions that Configuring takes during Putback transactions.
Table 8-5 Summary of Configuring Actions During a Putback Transaction
File in Parent |
File in Child |
Action by Configuring |
---|---|---|
Exists |
Does not exist |
Block Putback and notify user |
Does not exist |
Exists |
Create the file in the parent |
Unchanged |
Unchanged |
None |
Unchanged |
Changed |
Update file in the parent. (Merge SCCS files and extract [via get] a g-file that consists of the most recent delta.) |
Changed |
Unchanged |
Block Putback, notify user. |
Changed |
Changed |
Block Putback, notify user. |
Checked out |
Checked out* |
Block Putback, notify user. |
Unresolved conflict |
Unresolved conflict** |
Block Putback, notify user. |
*If a file is checked out in either the parent or the child, the transaction is blocked. See Table 8-4 for more information about putting back files that are checked out.
**If a conflict is unresolved in either the parent or the child, the transaction is blocked.