Importing a subversion repository where some branches come from trunk subtrees

Hello,

I noticed that a svn branch made out of a subtree of trunk confuses
git-svn which fetches the whole history a second time (restricted to
that subtree). Unfortunately this kind of strange branching has been
repeatedly made in the Blender svn repository and I can end up with 5
or 6 times the full history from rev1 to rev20000, which makes the
conversion even slower, the mirror bigger and loooong to clone and
bisects completely unuseful.

Is this expected ? Or when git-svn identified the svn revision number
of the parent and there already is a git commit imported from this
revision, should it use that commit as the parent ? This would make
the branch creation commit have a big "mangling paths" diff with its
parent but I think it is logical.

That also means that when importing a revision, git-svn should always
import the state of the whole tree (up to the branch, tag, or trunk
root) and not only a part of it.

I have made a 4-revision sample svn repo which exhibits the problem,
but it is quite simple to reproduce.

Is there a good reason for this behaviour (in other cases I can't think of) ?


Julien "_FrnchFrgg_" Rivaud