General options
~~~~~~~~~~~~~~~
-All commands except clone accept this option.
+All commands except clone accept these options.
--git-dir <dir>::
Set the 'GIT_DIR' environment variable. See linkgit:git[1].
+--verbose::
+ Provide more progress information.
+
Sync options
~~~~~~~~~~~~
These options can be used in the initial 'clone' as well as in
+
This example imports a new remote "p4/proj2" into an existing
git repository:
++
----
$ git init
$ git p4 sync --branch=refs/remotes/p4/proj2 //depot/proj2
--silent::
Do not print any progress information.
---verbose::
- Provide more progress information.
-
--detect-labels::
Query p4 for labels associated with the depot paths, and add
them as tags in git. Limited usefulness as only imports labels
~~~~~~~~~~~~~~
These options can be used to modify 'git p4 submit' behavior.
---verbose::
- Provide more progress information.
-
--origin <commit>::
Upstream location from which commits are identified to submit to
p4. By default, this is the most recent p4 commit reachable
Re-author p4 changes before submitting to p4. This option
requires p4 admin privileges.
---export-labels:
+--export-labels::
Export tags from git as p4 labels. Tags found in git are applied
to the perforce working directory.
enabled. Each entry should be a pair of branch names separated
by a colon (:). This example declares that both branchA and
branchB were created from main:
++
+-------------
+git config git-p4.branchList main:branchA
+git config --add git-p4.branchList main:branchB
+-------------
git-p4.ignoredP4Labels::
List of p4 labels to ignore. This is built automatically as
git-p4.importLabels::
Import p4 labels into git, as per --import-labels.
-git-p4.validLabelRegexp::
+git-p4.labelImportRegexp::
Only p4 labels matching this regular expression will be imported. The
- default value is '[A-Z0-9_\-.]+$'.
-
--------------
-git config git-p4.branchList main:branchA
-git config --add git-p4.branchList main:branchB
--------------
+ default value is '[a-zA-Z0-9_\-.]+$'.
git-p4.useClientSpec::
Specify that the p4 client spec should be used to identify p4
user map, 'git p4' exits. This option can be used to force
submission regardless.
-git-p4.attemptRCSCleanup:
+git-p4.attemptRCSCleanup::
If enabled, 'git p4 submit' will attempt to cleanup RCS keywords
($Header$, etc). These would otherwise cause merge conflicts and prevent
the submit going ahead. This option should be considered experimental at
git-p4.exportLabels::
Export git tags to p4 labels, as per --export-labels.
-git-p4.validLabelRegexp::
+git-p4.labelExportRegexp::
Only p4 labels matching this regular expression will be exported. The
- default value is '[A-Z0-9_\-.]+$'.
+ default value is '[a-zA-Z0-9_\-.]+$'.
IMPLEMENTATION DETAILS
----------------------