Snerp Vortex's Git replayer treats branches like directories, since that's what they are in Subversion. This makes Snerp's repositories much larger than the original Subversion ones.
Explore ways to do real branching in the Git replayer. Perhaps something like this for a start:
If a copy creates a branch...
... and the copy source is the root path for an entity...
... then the entity has been branched.
In that case, create a branch rather than copy the entity.
Subversion's ability to copy files across branches is a form of merging. How does this map to Git?
Snerp Vortex's Git replayer treats branches like directories, since that's what they are in Subversion. This makes Snerp's repositories much larger than the original Subversion ones.
Explore ways to do real branching in the Git replayer. Perhaps something like this for a start:
If a copy creates a branch... ... and the copy source is the root path for an entity... ... then the entity has been branched.
In that case, create a branch rather than copy the entity.
Subversion's ability to copy files across branches is a form of merging. How does this map to Git?