title: Why would svn merge of a branch with no changes causes untouched files to modify svn:mergeinfo property
body: <p>I have created a branch called "feature3" from my trunk.  I make zero modifications to files on the "feature3" branch.  There are also no modifications to files on trunk.  Using TortoiseCVS (TortoiseSVN 1.6.6, Build 17493 - 32 Bit) against a SVN (version 1.6.3 (r38063)) repo, I initiate a "Merge" with the "Reintegrate a branch" option selected.</p>
  
  <p>The output of this command shows 80 files merged.  The only thing changed on these files is the svn:mergeinfo property.  But why only these 80 files?  I have hundreds of other files in the project that didn't have this property changed.</p>
  
  <p>Here is an example of the change to the svn:mergeinfo property on a single file</p>
  
  <p>Before:</p>
  
  <blockquote>
    <p>/trax/branches/current/Libraries/Security/Specifications/NotSpecification.cs:10292-10783
    /trax/branches/feature1/Libraries/Security/Specifications/NotSpecification.cs:11324
    /trax/branches/feature2/Libraries/Security/Specifications/NotSpecification.cs:11326
    /trax/branches/int/Libraries/Security/Specifications/NotSpecification.cs:11232-11314
    /trax/branches/next/Libraries/Security/Specifications/NotSpecification.cs:10156-10782
    /trax/branches/trax-1.0.x/Libraries/Security/Specifications/NotSpecification.cs:10191-10291
    /trax/branches/upgrade/Libraries/Security/Specifications/NotSpecification.cs:9964-10604
    /trax/tags/trax-1.0.0/Libraries/Security/Specifications/NotSpecification.cs:10178-10190
    /trax/trunk/Libraries/Security/Specifications/NotSpecification.cs:6672-9851,11232-11325</p>
  </blockquote>
  
  <p>After</p>
  
  <blockquote>
    <p>/trax/branches/current/Libraries/Security/Specifications/NotSpecification.cs:10292-10783
    /trax/branches/feature1/Libraries/Security/Specifications/NotSpecification.cs:11324
    /trax/branches/feature2/Libraries/Security/Specifications/NotSpecification.cs:11326
    /trax/branches/feature3/Libraries/Security/Specifications/NotSpecification.cs:11328-11334
    /trax/branches/int/Libraries/Security/Specifications/NotSpecification.cs:11232-11314
    /trax/branches/next/Libraries/Security/Specifications/NotSpecification.cs:10156-10782
    /trax/branches/trax-1.0.x/Libraries/Security/Specifications/NotSpecification.cs:10191-10291
    /trax/branches/upgrade/Libraries/Security/Specifications/NotSpecification.cs:9964-10604
    /trax/tags/trax-1.0.0/Libraries/Security/Specifications/NotSpecification.cs:10178-10190
    /trax/trunk/Libraries/Security/Specifications/NotSpecification.cs:6672-9851,11324-11327</p>
  </blockquote>
  
  <p>The changes are that this line was added</p>
  
  <blockquote>
    <p>/trax/branches/feature3/Libraries/Security/Specifications/NotSpecification.cs:11328-11334</p>
  </blockquote>
  
  <p>and the last line was modified</p>
  
  <blockquote>
    <p>/trax/trunk/Libraries/Security/Specifications/NotSpecification.cs:6672-9851,11324-11327</p>
  </blockquote>
  
  <p>I expected that the merge would result in zero files being merged.  <strong>Why would SVN think that these files need to be merged and their svn:mergeinfo property changed?  Is there a way to correct this?</strong></p>
  
  <p>Is this a case where I should delete the svn:mergeinfo properties on all 80 files?  I am alluding to <a href="https://stackoverflow.com/questions/767418/remove-unnecessary-svnmergeinfo-properties">here</a> and <a href="https://stackoverflow.com/questions/391864/svn-mergeinfo-properties-on-paths-other-than-the-working-copy-root">here</a>.</p>
  
  <p>This trivial example is a part of a larger investigation in which I create a feature branch, make several changes and then attempt to merge changes back to the trunk.  However, the merge informs me of several tree conflicts on these same 80 files.  This is all very frustrating that I cannot use SVN branching due to all these tree conflicts.</p>