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

'svn log -g' should more gracefully and conservatively handle invalid mergeinfo source paths

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.5.x
    • Fix Version/s: 1.7.0
    • Component/s: libsvn_repos
    • Labels:

      Description

      Alexander Kitaev <Alexander.Kitaev {at} svnkit.com> reported on IRC and then on
      dev@ a problem with 'svn log -g' caused by having a not-found mergeinfo source
      path in the svn:mergeinfo property.  While we designed 'svn log -g' to
      gracefully handle such cases (not erroring out), we might have overshot -- 'svn
      log -g' should be able to recurse on paths that do exist, and avoid recursion
      only on those that don't (instead of the current state, where it's an
      all-or-nothing approach).
      

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              cmpilato C. Michael Pilato
              Reporter:
              cmpilato C. Michael Pilato

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment