Detecting Perforce unopened modified files

perforce
cdleary picture cdleary · Nov 5, 2008 · Viewed 21k times · Source

I'm trying to figure out a way to detect files that are not opened for editing but have nevertheless been modified locally. p4 fstat returns a value headModTime for any given file, but this is the change time in the depot, which should not be equal to the filesystem's stat last modified time.

I'm hoping that there exists a more lightweight operation than backing up the original file, forcing a sync of the file, and then running a diff. Ideas?

Answer

grieve picture grieve · Nov 5, 2008

From: http://answers.perforce.com/articles/KB/3481/?q=disconnected&l=en_US&fs=Search&pn=1

See step 2 specifically:

2 . Next, open for "edit" any files that have changed:

p4 diff -se //myclient/... | p4 -x - edit

p4 diff -se returns the names of depot files whose corresponding client file differs in any way from the clients #have revision.

Related questions

How to delete a workspace in Perforce (using p4v)?

I'm new to Perforce and have created a few workspaces as exercises for getting familiar with it. Now I would like to delete some of the workspaces. I just want to get rid of the workspaces so that they do …

Read More
What is the difference between "Rollback..." and "Back Out Submitted Changelist #####" in Perforce P4V

I want to reverse the changes from one of my checkins. In the right-click context menu of the particular changelist, there are these two options: Rollback... Back Out Submitted Changelist What is the difference between these two? In what situations …

Read More
GIT vs. Perforce- Two VCS will enter... one will leave

So I'm in the process of getting GIT sold at work. First thing I need is to convince everyone that GIT is better at what they're already used to doing. We currently use Perforce. Anybody else go through a similar …

Read More