Uploaded image for project: 'Subversion'
  1. Subversion
  2. SVN-3032

merge from a renamed branch fails while avoiding repeat merges from renamed path

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • ---
    • 1.5.0
    • libsvn_client
    • None

    Description

      <snip from subversion/libsvn_client/merge.c in do_directory_merge>
           while (end_rev != SVN_INVALID_REVNUM)
              {
                svn_revnum_t next_end_rev;
                svn_pool_clear(iterpool);
      
                /* Use persistent pool while playing with remaining_ranges. */
                slice_remaining_ranges(children_with_mergeinfo, is_rollback,
                                       end_rev, pool);
                notify_b->cur_ancestor_index = -1;
                SVN_ERR(drive_merge_report_editor(merge_b->target,
                                                  url1, start_rev, url2, end_rev,
                                                  children_with_mergeinfo,
                                                  is_rollback,
                                                  depth, notify_b, adm_access,
                                                  &merge_callbacks, merge_b,
                                                  iterpool));
      
      </snip>
      
      In the above snip we use same url1 and url2 even though they correspond to
      revision1 and revision2 only for each run. It may be incorrect for start_rev and
      end_rev.
      

      Original issue reported by kameshj

      Attachments

        1. 1_test2.sh
          0.7 kB
          Subversion Importer

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            subversion-importer Subversion Importer
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment