Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.5.x
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
Attachments
Issue Links
- is duplicated by
-
SVN-3789 log -g regression in r1028108
- Closed