Flags for the sync command.
Namespace: Perforce.P4Assembly: p4api.net (in p4api.net.dll) Version: 2015.1.103.4687 (2015.1.103.4687)
Syntax
| C# |
|---|
[FlagsAttribute] public enum SyncFilesCmdFlags |
| Visual Basic |
|---|
<FlagsAttribute> _ Public Enumeration SyncFilesCmdFlags |
| Visual C++ |
|---|
[FlagsAttribute] public enum class SyncFilesCmdFlags |
Members
| Member name | Value | Description | |
|---|---|---|---|
| None | 0 | No flags. | |
| Force | 1 | The -f flag forces resynchronization even if the client already has the file, and overwriting any writable files. This flag doesn't affect open files. | |
| ProcessLikeLabel | 2 | The -L flag can be used with multiple file arguments that are in full depot syntax and include a valid revision number. When this flag is used the arguments are processed together by building an internal table similar to a label. This file list processing is significantly faster than having to call the internal query engine for each individual file argument. However, the file argument syntax is strict and the command will not run if an error is encountered. | |
| Preview | 4 | The -n flag previews the operation without updating the workspace. | |
| ServerOnly | 8 | The -k flag updates server metadata without syncing files. It is intended to enable you to ensure that the server correctly reflects the state of files in the workspace while avoiding a large data transfer. Caution: an erroneous update can cause the server to incorrectly reflect the state of the workspace. | |
| PopulateClient | 16 | The -p flag populates the client workspace, but does not update the server to reflect those updates. Any file that is already synced or opened will be bypassed with a warning message. This option is very useful for build clients or when publishing content without the need to track the state of the client workspace. | |
| Quiet | 32 | The -q flag suppresses normal output messages. Messages regarding errors or exceptional conditions are not suppressed. | |
| SafeMode | 32 | The -s flag adds a safety check before sending content to the client workspace. This check uses MD5 digests to compare the content on the clients workspace against content that was last synced. If the file has been modified outside of Perforce's control then an error message is displayed and the file is not overwritten. This check adds some extra processing which will affect the performance of the operation. |
