diff options
author | Simon Hausmann <hausmann@kde.org> | 2007-03-23 09:16:07 +0100 |
---|---|---|
committer | Simon Hausmann <hausmann@kde.org> | 2007-03-23 09:16:07 +0100 |
commit | 9512497bcf574a2f70e43be0bcb58e35fb6aaba8 (patch) | |
tree | 0072decca072386b72b01239d7a8d3abd5364823 /contrib/fast-import/git-p4.txt | |
parent | 179caebff4a917dc35c8166ec183bc5c76df53e1 (diff) | |
download | git-9512497bcf574a2f70e43be0bcb58e35fb6aaba8.tar.gz git-9512497bcf574a2f70e43be0bcb58e35fb6aaba8.tar.xz |
Make it possible to run git-p4 submit from within the git repository
Signed-off-by: Simon Hausmann <hausmann@kde.org>
Diffstat (limited to 'contrib/fast-import/git-p4.txt')
-rw-r--r-- | contrib/fast-import/git-p4.txt | 27 |
1 files changed, 13 insertions, 14 deletions
diff --git a/contrib/fast-import/git-p4.txt b/contrib/fast-import/git-p4.txt index 4319c82dc..8bf0805c7 100644 --- a/contrib/fast-import/git-p4.txt +++ b/contrib/fast-import/git-p4.txt @@ -51,28 +51,27 @@ Submitting git-p4 has EXPERIMENTAL support for submitting changes from a git repository back to a Perforce depot. This requires a Perforce checkout separate to your -git repository. This is the basic procedure: +git repository. All it should take is calling - cd path/to/your/perforce/checkout - git-p4 submit --git-dir=/path/to/your/git/repository + git-p4 submit -This will create a temporary git branch, use git-rev-list to find out which git -commits are in your current branch but not in the "origin" branch. You can -override the name of the "origin" branch by using the --origin=mybranch option. -The "origin" branch has to be the branch populated with git-p4's sync -operation. +in your git repository. This will attempt to locate the perforce checkout +corresponding to your imported depot path. By default the changes between your +current branch and the "p4" branch will be submitted. If there is no "p4" +branch the "origin" branch will be used as reference instead. You can override +this with the --origin=mysourcebranch option. The "origin" branch has to be the +branch populated with git-p4's sync operation. After some preparations (which might take a while) git-p4 enters a loop where it will first show a Perforce submit template and a diff of the change to -apply. After quitting the pager with 'q' git-p4 asks for confirmation for -issuing the "p4 submit" command and also gives you the option of editing the -submit template using "e". +apply in the editor. After saving and exiting the editor you will be asked whether +you really want to submit the change or not. If a submit fails you may have to "p4 resolve" and submit manually. You can continue importing the remaining changes with - git-p4 submit --git-dir=/path/to/your/git/repository --continue + git-p4 submit --continue -After submitting you should sync your origin branch from Perforce using -git-p4's sync command. +After submitting you should sync your perforce import branch ("p4" or "origin") +from Perforce using git-p4's sync command. |