I think you've misinterpreted the OP or the purpose of svn-git -- that programming language metaphor doesn't work at all.
Rather, everybody at his job uses Notepad and he'd like to use vim. It improves his performance and affects nobody else.
Rather, everybody at his job uses Notepad and he'd like to use vim. It improves his performance and affects nobody else.
I have found in the workplace it is better to stick to what they supply and ask you to use and change it by pushing people in the right direction then to assume you know better and do your own thing.
Look at it from the employeers perspective. If you say use SVN and someone says "Pffft I will use GIT" and then they loose a days work because of it who am I going to blame?
Ever considered that you might be wrong on both counts?
Arguing that the 'main' repo has to be git is a tough sell, but I think we'll get there eventually, once we show how much easier experimental branching, disconnected operation, distributed nature etc will be advantageous to us.
The git-svn solution is pretty good, because the main repo will be svn, and people who are used to svn (and like the restrictions that come with it) will be happy as well. Git users will also be able to get all the benefits of using it..
The other alturnative is to check out using SVN, check that into GIT, do your changes as normal from here and when finished check back into SVN. You only branch and so forth on your local machine but it also ensures you dont break the main repo.