As I said, I didn't experience an overhead. In SVN, you normally need one step to prepare the directory for SVN import (e.g. the trunk/ branch/ merge directory structure) which somehow would correspond to git init. To publish it, svn import would correspond to git clone -bare.

Your couple of dozen scripts are all unrelated? So there is no group of scripts your colleagues would likely want to fetch together?

What I meant with my history comment was, I also used to have a single big SVN repository for almost everything. My SVN dump was huge at the end. But for most projects, I never actually needed the history later on. Now I have a decent backup system and git when version control is actually needed (collaboration, branching etc.). So much cleaner and better...