[PATCH] git-p4: fix issue with multiple perforce remotes

From: Kirill Frolov <k.frolov@samsung.com>

Single perforce branch might be sync'ed multiple times with different revision numbers, so it will be seen to Git as complete different commits. This can be done by the following command:

  git p4 sync --branch=NAME //perforce/path...

It is assumed, that this command applied multiple times and peforce repository changes between command invocations.

In such situation, git p4 will see multiple perforce branches with same name and different revision numbers. The problem is that to make a shelve, git-p4 script will try to find "origin" branch, if not specified in command line explicitly. And previously script selected any branch with same name and don't mention particular revision number. Later this may cause failure of the command "git diff-tree -r $rev^ $rev", so shelve can't be created (due to wrong origin branch/commit).

This commit fixes the heuristic by which git p4 selects origin branch: first it tries to select branch with same perforce path and perforce revision, and if it fails, then selects branch with only same perforce path (ignoring perforce revision number).

Signed-off-by: Kirill Frolov <k.frolov@samsung.com>
---
    git-p4: fix issue with perforce branch synchronized multiple times.
    
    Perforce branch might be sync'ed multiple times with different revision
    numbers (by the command "git p4 sync --branch=NAME //perforce/path...")
    
    In such situation, git p4 will see multiple perforce branches with same
    name and different revision numbers. The problem is that to make a
    shelve, git-p4 script will try to find "origin" branch, if not specified
    in command line explicitly. And previously script selected any branch
    with same name and don't mention particular revision number. Later this
    may cause failure of the command "git diff-tree -r $rev^ $rev", so
    shelve can't be created (due to wrong origin branch/commit).
    
    This commit fixes the heuristic by which git p4 selects origin branch:
    first it tries to select branch with same perforce path and perforce
    revision, and if it fails, then selects branch with only same perforce
    path (ignoring perforce revision number).
    
    Signed-off-by: Kirill Frolov k.frolov@samsung.com

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1180%2Fkfrolov%2Fperforce_multi_fix-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1180/kfrolov/perforce_multi_fix-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1180

 git-p4.py | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)