Helix Core is now P4. Product user interfaces will be updated soon. Learn more >>

P4 Visual Client (P4V) Documentation | 2025.4

# Repo file information

A repo file is displayed like this:

`filename.txt #haveBlob/headBlob`

where a file is represented as a binary large object (`blob`):

Repo | Client
--- | ---
`headBlob` represents the SHA-1 for the file content at the head revision | `haveBlob` represents the SHA-1 for the file content at the have revision on the client
`headCommit` represents the commit SHA-1 for the file at the head revision | `haveCommit` represents the commit SHA-1 for the file at the have revision on the client

In the depot tree tab, if file shows `#none/headBlob`, it means the file exists in the depot but it's not currently synced based on current tag or SHA-1.

means that the repo file is both at `headBlob` and at `headCommit`, such that `haveBlob` matches `headBlob` and `haveCommit` matches `headCommit`: |
means that the repo file is at `headBlob` but not at `headCommit`, such that `haveBlob` matches `headBlob` but `haveCommit` does not match `headCommit` In this case, just as with a classic file, you must sync to get latest before submitting. |
means that the repo file is not at `headBlob` and not at `headCommit`, such that `haveBlob` does not match `theheadBlob` and `haveCommit` does not matche `headCommit` |

Your search for returned results