You have two options. You can use the git-svn bridge or manage your own patches. git-svn has a lot of good features that are specific to it, so it’s worth lea

You have two options. You can use the git-svn bridge or manage your own patches. git-svn has a lot of good features that are specific to it, so it’s worth learning it like a new tool rather than a git feature. Get comfortable with it from some tutorials, then read the man page from top to bottom. It’s worth it. The cheapo version is to git init and checkout of your source code, pretend it’s a git project, and then produce a patch for your branch at the end. You might even be able to use svn and git commands in the same directory? git for managing your private “work in progress” branches, locally, and svn to track upstream and submit work.