Re: how issue-2897 branch solves reflective merges?
From: Kamesh Jayachandran <kamesh_at_collab.net>
Date: Fri, 11 Jan 2008 18:43:26 +0530
>> Case3:
We are not applying the r17, sorry if I worded it that way. Following
Consider the case
b. Create feature branch /feature_branch from /trunk
c. Modify /trunk/test.c line1 -> tline1 at r13
d. Modify /trunk/test.c line2 -> tline2 at r17
e. Modify /trunk/test.c line3 -> tline3 at r29
f. Modify /feature_branch/test.c line2 ->fbline2 commit at r30.
g. merge /trunk r13 to /feature_branch working copy. NO COMMIT
h. merge /trunk r17 to /feature_branch working copy. This would give
i. merge /trunk r29 to /feature_branch working copy. COMMIT at r40
j. merge /feature_branch to /trunk working copy.
r40 is merged with reflective call back.
reflective_merge_file_changed(mine, older, yours)
mine = 'tline1\ntline2\ntline3'
After merging r13 older='tline1\nfbline2\nline3'
diff(older, yours) = "@@ -1,3 +1,3 @@
Which would give raise to a conflict as trunk does not have 'fbline2'.
Thanks
With regards
---------------------------------------------------------------------
|
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.