[p4] Detecting files that were modified but not checked out

[Noah Salzman]

On May 19, 2006, at 10:07 AM, Edil Cadenas wrote:

> Does anyone know if there is a way to find all files in the workspace
> that have been modified without being checked out?  We use certain
> scripts that require files to be modified without being checked out so
> what our users do is to change the attributes of workspace files to
> writeable.
>
> In VSS, there is a tool to find these files that were modified but  
> were
> not checked out.  ClearCase also detects these files.  Does anyone  
> know
> if such functionality also exists in Perforce?
>


There was just a long thread (mostly) on this subject just a couple  
weeks ago. Search the mail archives at Perforce for "perforce vs  
subversion".

Here is a highlight:


On May 4, 2006, at 3:00 PM, Weintraub, David wrote:
> If you're on Unix:
>
> $ find . -type f | p4 -x - files > /dev/null
>
> If you're on Windows:
>
> $ dir /B/A-D/S | p4 -x - files > NUL
>
> The error output will show files that are local, but not in  
> Perforce. A
> bit fancier on Unix:
>
> $ $ (find . -type f | p4 -x - files > /dev/null) 2>&1 | sed 's/ - .* 
> $//'
>
> This moves the files to STDOUT and removes the error message. That  
> way,
> you could use this as an input to another pipe.