This post is part of a series on Git and Subversion. To see all the related posts, screencasts and other resources, please click here.
Time to whip out the last two screencasts for this round. Here's the first of the two, hopefully the second one will be out later this evening.
Depending on the complexity of the history of your own Subversion projects, undertaking this kind of "archeology" might seem intimidating. At work, we have a rather large SVN project which has been thrown around different locations, split into 30 projects, merged back together again, and moved again on a regular basis. I once began digging through this to get all history into Git, but gave up after two modules. It simply wasn't worth it before we're ready to do a complete migration (leaving SVN behind, which is the topic of the next screencast).
So, for now, I haven't got the *entire* SVN history in the Git repository. But it doesn't matter, I can still work productively with Git, and we can always get the old history later on when we're willing to invest the time.