git svn's performance on cloning mono's branches/tags...

(I'm not on list so please CC) - I am trying to git svn clone mono's repository, and for some strange reason it is doing a complete check out from revision 1 all the way to each branch/tag . Is this normal or am I doing anything wrong? I have git svn clone a few other things recently (R, ghostscript) and I don't remember git doing this, but R is quite a normal svn layout and I think I only have ghostcript trunk (no branch/tag).

What I did was this: I started out with just git-svn clone trunk (which generated the first two [now-commented out] lines), then I thought I also want 2.4 branch so I added the next commented-out section, and ran 'git svn fetch --all'. Then I thought I like the whole thing - so I commented out most of it and added the 4 lines as blow - which is also my current git config.

The problem is that it seems to treat every tag as a branch, and also seem to want to check out every revision from r1 up to r3382 for MONO_0_10, etc. to mono/tags/MONO_0_10@3382 , and r1 to r2598 for mono/tags/MONO_0_9@2598 , etc.

--------------------------------------------------------------------
[svn-remote "svn"]
#	url = svn://anonsvn.mono-project.com/source/trunk/mono
#	fetch = :refs/remotes/git-svn
  url = svn://anonsvn.mono-project.com/source
  tags = tags/*/mono:refs/remotes/mono/tags/*
  branches = branches/*/mono:refs/remotes/mono/branches/*
  trunk = trunk/mono:refs/remotes/git-svn
#[svn-remote "mono24"]
#	url = svn://anonsvn.mono-project.com/source/branches/mono-2.4/mono
#	fetch = :refs/remotes/git-svn-mono24
--------------------------------------------------------------------

I guess my ultimate question is, how does one modify git config to track tags and branches, etc as well, *after* having already svn clone'd trunk?, without burning too much bandwidth?