1git-p4.py - Perforce <-> Git converter using git-fast-import
23
Usage
4=====
56
git-p4 supports two main modes: Importing from Perforce to a Git repository is
7done using "git-p4.py sync". Submitting changes from Git back to Perforce is
8done using "git-p4.py submit".
910
Importing
11=========
1213
The procedure is simple:
1415
mkdir repo-git
16cd repo-git
17git init
18git-p4.py sync //path/in/your/perforce/depot
1920
This will import the current head revision of the specified depot path into the
21master branch of your git repository. You can use the --branch=mybranch option
22to let git-p4 import from Perforce into a git branch of your choice.
2324
If you want to import the entire history of a given depot path just use
2526
git-p4.py sync //path/in/depot@all
2728
29
Support for Perforce integrations is still work in progress. Don't bother
30trying it unless you want to hack on it :)
3132
33
Incremental Imports
34===================
3536
After an initial import you can easily synchronize your git repository with
37newer changes from the Perforce depot by just calling
3839
git-p4.p4 sync
4041
in your git repository. git-p4 stores the depot path of the original import in
42the .git/config file and remembers the last imported p4 revision as a git tag
43called p4/<changenum> .
4445
Submitting
46==========
4748
git-p4 has EXPERIMENTAL support for submitting changes from a git repository
49back to a Perforce depot. This requires a Perforce checkout separate to your
50git repository. This is the basic procedure:
5152
cd path/to/your/perforce/checkout
53git-p4.py submit --git-dir=/path/to/your/git/repository
5455
This will create a temporary git branch, use git-rev-list to find out which git
56commits are in your current branch but not in the "origin" branch. You can
57override the name of the "origin" branch by using the --origin=mybranch option.
58The "origin" branch has to be the branch populated with git-p4's sync
59operation.
6061
After some preparations (which might take a while) git-p4 enters a loop where
62it will first show a Perforce submit template and a diff of the change to
63apply. After quitting the pager with 'q' git-p4 asks for confirmation for
64issuing the "p4 submit" command and also gives you the option of editing the
65submit template using "e".
6667
If a submit fails you may have to "p4 resolve" and submit manually. You can
68continue importing the remaining changes with
6970
git-p4.py submit --git-dir=/path/to/your/git/repository --continue
7172
After submitting you should sync your origin branch from Perforce using
73git-p4's sync command.
74