svn:mergeinfo is not being cherry-picked properly between branches -


i created ^sandbox/feature-branch ^trunk staging area proof of concept.

but don't want reintegrate merge feature branch ^trunk because of sandbox in name.

i'd create ^branches/feature-branch , cherry-pick changes 1 one ^sandbox/feature-branch.

and reintegrate merge nicer named ^branches/feature-branch down ^trunk.

in testing can acquire change set svn:mergeinfo not expect. not include svn:mergeinfo entries added ^sandbox/feature-branch commits.

creation scenario

working copy: ^sandbox/feature-branch

cherry pick code ^branches/another-feature-branch

this gives commit changes , adds svn:mergeinfo entry this: /branches/another-feature-branch:1234

cherry pick scenario

working copy: ^branches/feature-branch

cherry pick code ^sandbox/feature-branch

this takes change svn:mergeinfo change not expect: /sandbox/feature-branch:2345

but there no mention change came ^branches/another-feature-branch:1234

is there way original merge path included when cherry-picking commits in subversion?

fix expectations: mergeinfo always reflect only p2p-exchange of data on merge between source , target of operation , doesn't handle ancestors of source commit

is there way original merge path included when cherry-picking commits in subversion?

no (internally), , isn't needed really. can edit mergeinfo hand, if want have such additional useless bells&whistles


Comments

Popular posts from this blog

java - Run a .jar on Heroku -

java - Jtable duplicate Rows -

validation - How to pass paramaters like unix into windows batch file -