Open mono-princess opened 4 years ago
You probably need a rule before the other tag rules for /Project/tags/([^/]+)/$
with action recurse
.
A tag is usually a copy of the entire directory like /Project/trunk => /Project/tags/tag-1
.
In this case svn2git
does only see these paths and your tag rules do not match.
You have to tell it to recurse into the directories to identify the actual rules to apply.
As for the skip message, I have no idea without a reproduction script.
The structure of my svn repository looks similar to this:
In reality there are several branches and several tags. Most of the tags were generated after the branches and the name of these tags is the same as the corresponding branch. The repository has over 26000 revisions.
The svn-repository is splitted into several git repositories (in total 8) where some of the directories (
dir1, ..., dir<n>
) were grouped together, for example:Here is the rules file for this repository:
Results:
After performing the migration not all the tags were fetched into the corresponding git-repositories.
In the logs there was found a message the following message for some repositories:
recursiveDumpDir: "/Project/tags/tag_1/dir2/" skip entry for different/ignored repository
Questions:
Why are the tags not fetched?
Why did the message
recursiveDumpDir
appear in the logs even though none of the match definitions contains the parameteraction export
and all them have defined the parameterrepository
?