CODEWITHSUNDEEP
perforce
Adam Naylor
Adam Naylor

Reputation: 6340

How to reconcile newer workspace files with depot in Perforce?

I have a situation where my depot is saying it has the latest version of a bunch of different files but my local workspace actually has newer revisions. My tools (P4V and VS plugin) are incorrectly telling me that everything is up-to-date.

I can prove this is the case because if I check out the file, make no changes, and submit, the changes are committed and the history appears correct and get latest operations on other machines pull the correct version of the file.

This isn't really a viable solution as there could be many files that require this fix and I have no way of knowing I have fixed them all.

I believe the issue has come about due to occasionally working offline and (incorrectly) twiddling the read only flag on the file when I needed to make a change.

So my question:

Is there a command (or similar) I can run that will look at my workspace files and see that there is a change that hasn't been committed. Essentially ignoring the 'reported' state of the file? Something like sync but in reverse? This would allow me to 'force commit' all those files and get the depot in the correct state.

Upvotes: 2

Views: 1364

Answers (1)

Bryan Pendleton
Bryan Pendleton

Reputation: 16389

The command you are looking for is called 'p4 reconcile'. Here's some background information: Working Disconnected from the Perforce Server.

Upvotes: 2

Related Questions