RFC: Quick question on how --reintegrate merges should behave
From: Paul Burba <ptburba_at_gmail.com>
Date: Tue, 18 Nov 2008 10:49:58 -0500
A quick question on how we'd prefer reintegrate merges to work:
Use Case 1:
Copy 'trunk_at_1' to 'branch' in r2
Then try to reintegrate 'branch' to 'trunk'. Should this:
A) Fail and require that r3 be merged from 'trunk' to 'branch' before
or
B) Merge the diff between 'trunk' and 'branch's youngest common
The current behavior is 'B'. Note that there is the possibility of a
~~~~~
Use Case 2:
Copy 'trunk_at_1' to 'branch' in r2
Then try to reintegrate 'branch' to 'trunk'. Should this:
A) Fail and require that r3 be merged from 'trunk' to 'branch' before
or
B) Fail with a message indicating that there is nothing to reintegrate
C) Actually do the merge of TRUNK_URL_at_1 BRANCH_URL_at_3 to 'trunk'. This
The current behavior is 'C'.
~~~~~
I think the current behavior in both use cases is correct and
merge_tests.py 80 'merge --reintegrate on a never-updated branch' -
merge_tests.py 85 'merge --reintegrate should fail on stale source' -
The merge_tests.py 85 test is currently marked as XFail. I think this
Paul
---------------------------------------------------------------------
|
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.