Cybersecurity
DevOps Cloud
IT Operations Cloud
PROBLEM/ABSTRACT:
A user modified an element, and the status never changed from backed to modified. What would cause the element to remain in a backed state?
SOLUTION:
This occurs if the element has a time stamp that preceded the workspaces update time. When this happens the element will remain "backed" in the modified filter. If you turn off optimization, this element will appear as "modified".
Example:
C:\ws_store\AccuRev_355_INT>dir
SNIP
05/19/2005 04:31 PM 75 test.txt
Copy a file with an older time stamp.
C:\ws_store\AccuRev_355_INT>dir
SNIP
02/25/2005 04:53 PM 7 test.txt
Now stat the file, it will still show as "backed" even though technically it had been modified.
C:\ws_store\AccuRev_355_INT>ac stat test.txt
.\test.txt AccuRev_355_QA\7 (5\4) (backed)
Now turn off optimization, the file will appear as modified.
C:\ws_store\AccuRev_355_INT>ac stat -O test.txt
.\test.txt AccuRev_355_QA\7 (5\4) (modified)
For further details regarding the stat command, please refer to the reference manual, section stat.
For more information contact AccuRev Support