git-svn: ignoring a bogus svn revision ?

Hello,

  I'm a frantic user of git-svn at work, as my company uses SVN as a
SCM for all of our projects. I've been very happily using git-svn over
our repositories since quite some time, and I think I managed to
convert a couple of colleagues by doing so.

  But now I'm facing an interesting issue. Our biggest repository has
over 102600 revisions, and initializing from scratch the git
repository up to this revision takes approximately 2 days of computer
work. The trouble begins with revision 102601... Up so far the
repository was in a perfect shape, and no one did any huge mistake. On
revision 102601 however, someone branched... /. Not /trunk, but /,
which means the whole nine yards, containing tags, branches, and
trunk.

  So I'm stuck with this:

repository-up-to-102600$ git branch -r | wc -l 1824

  And when I issue a git-svn fetch --no-follow-parent --revision
102601, git-svn starts trying to fetch all of these 1824 branches and
tag, obviously. I had to add the --no-follow-parent otherwise git-svn
would just go nuts. Now if it wasn't for the loosy svn server
disconnecting me after 2 or 3 days of work trying to check out this
branch, git-svn would probably manage to get over it. But the server
can't keep up it seems, and I eventually get disconnected, which means
I have to do it all over again.

  Of course, this svn commit is undeniably bogus, and no one will ever
be able to check it out and work on it for real. However, this doesn't
disrupt the usual course of work for other SVN users, but just
prevents anyone from using git-svn ever again on this repository.

  I've tried to look into how to remove/amend this svn revision
directly onto the server, but even if some documentation was telling
me how to do so (which isn't the case), our IS crew is just too
stubborn, and fills my requests back with "Please use a SVN client
supported by the IS crew; you can find links on this page...". I'm
still going to try to go through this path though, as I feel this is
probably the right thing to do, (apart holding my boss hostage in his
office until they finally decide to switch over to git completely, and
stop using a piece of software that allows you to push bogus commits)

  So on the other hand, I'm looking at how git-svn works, and I'm
trying to jump around this utterly bogus svn revision. I haven't found
any information at all about how I could skip this revision, and even
though I'm all willing to make some tests on the git repository itself
by tweaking it, I'd hate to leave it in a broken state that would
explode in my hands several weeks/month later. Thus I think I'd better
ask the authors directly, in order to know how I could achieve that in
a way that isn't too disruptive.

  Thanks!

  -- Nicolas Noble