How to find untracked files in a Perforce tree? (analogue of svn status)

by

EDIT: Please use p4 status now. There is no need for jumping through hoops anymore. See @ColonelPanic’s answer.

In the Jan 2009 version of P4V, you can right-click on any folder in your workspace tree and click “reconcile offline work…”

This will do a little processing then bring up a split-tree view of files that are not checked out but have differences from the depot version, or not checked in at all. There may even be a few other categories it brings up.

You can right-click on files in this view and check them out, add them, or even revert them.

It’s a very handy tool that’s saved my ass a few times.

EDIT: ah the question asked about scripts specifically, but I’ll leave this answer here just in case.

More Related Contents:

  1. Can you “ignore” a file in Perforce?
  2. What is the difference between all the different types of version control?
  3. When should you branch?
  4. Using IPython / Jupyter Notebooks Under Version Control
  5. ClearCase advantages/disadvantages [closed]
  6. Should I store generated code in source control
  7. What is the cleverest use of source repository that you have ever seen?
  8. IntelliJ IDEA 9/10, what folders to check into (or not check into) source control?
  9. Source control vs. Revision Control?
  10. What’s the best three-way merge tool? [closed]
  11. Storing third-party libraries in source control
  12. Mercurial for Beginners: The Definitive Practical Guide
  13. Best general SVN Ignore Pattern?
  14. Named Branches vs Multiple Repositories
  15. Mercurial — revert back to old version and continue from there
  16. Is version control (ie. Subversion) applicable in document tracking? [closed]
  17. Mercurial Subrepos – How do you create them and how do they work?
  18. What’s the easiest way to commit and push a single file while leaving other modifications alone?
  19. Mercurial: How to ignore changes to a tracked file
  20. How do I perform a recursive checkout using ClearCase?
  21. Is there a way to keep Hudson / Jenkins configuration files in source control?
  22. Branching Strategies [closed]
  23. Comparison between Centralized and Distributed Version Control Systems [closed]
  24. Mercurial: Merging one file between branches in one repo
  25. How often to commit changes to source control? [closed]
  26. Do you continue development in a branch or in the trunk? [closed]
  27. How should you build your database from source control?
  28. Getting started with Version Control System
  29. TFS 2017 – how build/deliver only changed files?
  30. Code version change “rules” [closed]

Leave a Comment