merge: do early copy to deal with issue636 Without copies/renames, merges source names are 1:1 with their targets. Copies and renames introduce the possibility that there will be two merges with the same input but different output. By doing the copy to the destination name before the merge, the actual merge becomes 1:1 again, and no source is the input to two different merges. - add a preliminary scan to applyupdates to do copies - for the merge action, pass the old name (for finding ancestors) and the new name (for input to the merge) to filemerge - eliminate the old post-merge copy - lookup file contents from new name in filemerge - pass new name to external merge helper - report merge failure at new name - add a test

     1

<table class="logEntry parity#parity#">

     2

 <tr>

     3

  <th class="age">#date|age# ago:</th>

     4

  <th class="firstline">#desc|strip|firstline|escape#</th>

     5

 </tr>

     6

 <tr>

     7

  <th class="revision">changeset #rev#:</th>

     8

  <td class="node"><a href="#url#rev/#node|short#{sessionvars%urlparameter}">#node|short#</a></td>

     9

 </tr>

    10

 #parent%changelogparent#

    11

 #child%changelogchild#

    12

 #changelogtag#

    13

 <tr>

    14

  <th class="author">author:</th>

    15

  <td class="author">#author|obfuscate#</td>

    16

 </tr>

    17

 <tr>

    18

  <th class="date">date:</th>

    19

  <td class="date">#date|date#</td>

    20

 </tr>

    21

 <tr>

    22

  <th class="files"><a href="#url#file/#node|short#{sessionvars%urlparameter}">files</a>:</th>

    23

  <td class="files">#files#</td>

    24

 </tr>

    25

</table>