What Features Do I loose With git-svn?

I want to use git for a project I am working on however because the project is going to possibility have a lot of binary content in size and number of files (game project), it is probably going to be hard to convince my team to make the switch since I have no real solution besides just use git for the code and svn for the binary data. I am hoping git-svn will do the trick for me. The question is are they any features I loose (like cherry picking) or anything that I have to look out for (does updating from svn cause merging issues just like working all in SVN does). Right now the only things I know to look out for is:

<ul> <li>Instead of git pull/push I have to use the git-svn equivalents</li> <li>If I have changes that are not in the index and I need to pull the latest code form SVN, I have to stash first, update from svn, and then apply the stash back.</li> </ul>

Any other things I have to look out for? I am mainly concerned that using git-svn will re-introduce the merge issues of SVN the git is great at doing.-- View this message in context: http://git.661346.n2.nabble.com/What-Features-Do-I-loose-With-git-svn-tp6317576p6317576.html Sent from the git mailing list archive at Nabble.com.