My project has a Subversion repository on a network file system, and a new team would like to access it using Git, and be able to commit to it and get updates from it.
W
You're better off with just having each developer learn to use git-svn
directly. There's simply too much of an impedance mismatch between the git and SVN models to be able to robustly implement what you are looking for. The only way you could get it to work even nearly reliably would be to enact the same sort of restrictions that git-svn
would have, but with more moving parts that could break. In my opinion, your revision control system is not the sort of thing that you want to be just partially reliable.
Alternatively just ditch SVN altogether and move all the way to git, if possible.