| commit | f271fad2661d2f26654e9b4b3ecb17ad0ea711e8 | |
| author | Steven Walter <stevenrwalter@gmail.com> | |
| Mon, 20 Aug 2012 01:39:40 +0000 (19 21:39 -0400) | ||
| committer | Eric Wong <normalperson@yhbt.net> | |
| Fri, 5 Oct 2012 22:48:12 +0000 (5 22:48 +0000) | ||
| tree | 456ee5748c2f344e12df5b90eb331b1b98649842 | treesnapshot (tar.gz zip) |
| parent | f84667def209e4a84e37e8488a08e9eca3f208c1 | commitdiff |
git-svn.perl: consider all ranges for a given merge, instead of only tip-by-tip
Consider the case where you have trunk, branch1 of trunk, and branch2 of
branch1. trunk is merged back into branch2, and then branch2 is
reintegrated into trunk. The merge of branch2 into trunk will have
svn:mergeinfo property references to both branch1 and branch2. When
git-svn fetches the commit that merges branch2 (check_cherry_pick),
it is necessary to eliminate the merged contents of branch1 as well as
branch2, or else the merge will be incorrectly ignored as a cherry-pick.
Signed-off-by: Steven Walter <stevenrwalter@gmail.com>
Reviewed-by: Sam Vilain <sam@vilain.net>
Signed-off-by: Eric Wong <normalperson@yhbt.net>
Consider the case where you have trunk, branch1 of trunk, and branch2 of
branch1. trunk is merged back into branch2, and then branch2 is
reintegrated into trunk. The merge of branch2 into trunk will have
svn:mergeinfo property references to both branch1 and branch2. When
git-svn fetches the commit that merges branch2 (check_cherry_pick),
it is necessary to eliminate the merged contents of branch1 as well as
branch2, or else the merge will be incorrectly ignored as a cherry-pick.
Signed-off-by: Steven Walter <stevenrwalter@gmail.com>
Reviewed-by: Sam Vilain <sam@vilain.net>
Signed-off-by: Eric Wong <normalperson@yhbt.net>
| perl/Git/SVN.pm | diffblobblamehistory | |
| t/t9165-git-svn-fetch-merge-branch-of-branch.sh | [new file with mode: 0755] | blob |