- <TITLE>Restricting Files Used in Commands</TITLE>
- <p> Many P4Web command option pages enable you to restrict the files that are
- be affected by the command. Depending on the command you are running, you have
- the following options:
- <ul>
- <li><b>All files: </b>Run the command on all files in your client view. </li>
- <p>
- <li><b>Files in <i>[path]</i> and subdirectories</b>: Restrict the command to
- the files in the current path and all subdirectories below the current path.
- </li>
- <p>
- <li><b>Files in <i>[path]</i> at this level only</b>: Restrict the command to
- the files at the current path level </li>
- <p>
- <li><b>Selected files</b>: Restrict the command to the files that are checked
- in the list that follows. In most cases this is the list of files at the current
- path level. On the Revert Options page this is the list of all your opened
- files at or below the current path level. </li>
- </ul>
- <dt> Regardless of which file restriction options you choose, commands affect
- only the files mapped in your <a href="client?help">client view</a>.
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 12234 | Matt Attaway | Rejigger P4Web project in preparation for official sunsetting The bin directory contain...s the last official builds of P4Web from the Perforce download site. P4Web is soon to be completely sunsetted; these builds are here for folks who don't want to build their own. To better handle the archived builds the source code has been moved into a separate src directory. « |
10 years ago | |
//guest/perforce_software/p4web/Help/restrictfiles.html | |||||
#1 | 8914 | Matt Attaway | Initial add of the P4Web source code | 11 years ago |