[SVN-3270] 'svn log -g' should more gracefully and conservatively handle invalid mergeinfo source paths

• 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: merge-tracking
• Assignee: C. Michael Pilato
• Reporter: C. Michael Pilato
• Created: 27/Aug/08 19:43
• Updated: 27/Oct/18 16:29
• Resolved: 28/Jan/11 19:45

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).

Issue Links

• is duplicated by: SVN-3789 log -g regression in r1028108