Overview
Artifact ID: | a0dafe1c57e861fdf45780468edd011c9de59483 |
---|---|
Ticket: | 74413366fe5067b3de2ee80567f15d432c7ea58d
Bad behaviour merging with renames |
User & Date: | anonymous 2011-01-04 09:53:45 |
Changes
- Appended to comment:
<hr /><i>anonymous claiming to be viric added on 2011-01-04 09:53:45 UTC:</i><br /> A diagram to understand the situation: <verbatim> [V]_ ^ \____ | ____[M] (the merge from P added B) | _/ | [P] | | | [rn A to B ] | | | [create A ] | | | | __[ . ] | / [ root ] </verbatim> So, looking at renames between P and M (with merges) does not have any rename in the way. But if we get the shortest path without merges (direct only), through root, there appears a rename "from B to A" (the reverse of the checkin). This rename makes the merge fail.