title: git svn dcommit without rebasing
body: <p>Our company uses (and supports!) SVN, but I tend to use git. What I want to try is to have git repository - one per project, project developers will be able to pull from this repository (and of course pull from each other if they will want to). But I still want to push all the changes to the SVN, because SVN is being maintained by our tech-support.</p>
  
  <p>I was testing the scenario with following repositories: </p>
  
  <ol>
  <li>SVN-repository - this one is maintained by our company and our team should push all changes there at some point  </li>
  <li>git-svn-clone - this is git repository cloned from SVN above - all project developers should push their commits here  </li>
  <li>git-dev-clone - this is developer's git repository.</li>
  </ol>
  
  <p>The only issue with straightforward usage of 'git svn rebase' and 'git svn dcommit' that I've noticed is that after each push from developer's git repository to the git-svn-clone repository I have to rebase developer's repository as soon as changes will be propagated to SVN and rebased. What I want to achieve is to avoid rebasing after each push. </p>
  
  <p>Please note that I'm assuming that every project developer will use only git repository and nobody will use SVN directly.</p>
  
  <p>I was able to achieve this behavior manually by checking out every git commit one by one in 'git-svn-clone' repository after push and committing those changes to the SVN using SVN client. I believe that 'git svn dcommit' does the same but it also syncs back from SVN and changes commit SHA identifiers which forces me to rebase.</p>
  
  <p>P.S.: <code>--no-rebase</code> option for <code>git svn dcommit</code> didn't help since after first commit propagated to SVN <code>git svn dcommit</code> didn't allow me committing more changes to the SVN until previous one was rebased. I've tried this behavior once and probably could overlook something.</p>