Normally you have access to the Perforce server, which controls read-write permission on files under its control. However, when you cannot connect to your Perforce server, you must set and unset read/write permission manually to modify these files. After working offline (without access to your Perforce server), you need to make sure that you bring your workspace and depot files into accord. To reconcile your workspace and the depot, you need to do the following:
Note: For renamed files, you must integrate the original file to the new filename and delete the original file. See Renaming and moving files or folders for more information.
You can diff your workspace with the depot to detect discrepancies between your workspace and the depot, as follows:
Files you created or renamed
in the workspace that are not in the depot
Files you deleted in the workspace
that are still present in the depot
Files you changed
in the workspace but have not checked into the depot
To reconcile your workspace and the depot:
If other users have also modified and checked in files that you changed, Perforce requires you to resolve the files to ensure that no changes are inadvertently overwritten.
Unmapped files
If your workspace contains unmapped files, they are listed in the Unmapped
folder: . Files
are unmapped, for example, if you synced them, then modified your client view
so that the workspace files are no longer mapped to depot files, or you created
files in your workspace that reside outside the directories mapped by your client
view. Exclusionary mappings do not cause files to be listed as unmapped.
Recommendation: Examine the contents of the Unmapped folder to determine whether it lists files that need to be added to your client view and checked in or, alternately, files that can be deleted from your workspace to conserve disk space and avoid confusion.