Fix incorrect SVN log parsing regexes
When importing a repository with non-standard paths, the parsing regexes
were incorrectly looking for filenames without a leading slash, and also
not looking for filenames with a slash after the branch/tag path.

Also, when importing standard repositories where the trunk/branches/tags
folders were not named in complete lower case, the regexes and logic for
finding those paths has been updated to be case-insensitive, and to
prefer using the same case as found in the repository for trunk.
1 parent 7b82522 commit a156d3c36a92038f5b7f2efdb9e5a2f173ac3e28
@John Reese John Reese authored on 12 Apr 2010
Showing 1 changed file
View
SourceSVN/SourceSVN.php