title: msysgit git-am can't apply it's own git format-patch sequence
body: <p>I'm using <em>msysgit</em> git on windows to operate on central svn repository. I'm using git as
  I want to have it's awesome little local branches for everything and rebasing on each other.</p>
  
  <p>I also need to update from central repo often, so using separate svn/git is not an option.</p>
  
  <p>Problem is - <code>git svn --help</code> (man page) says that it is not a good idea to use <code>git merge</code> into <em>master</em> branch (which is set to track from svn's <em>trunk</em>) from local branches, as this will ruin the party and <code>git svn dcommit</code> would not work anymore.</p>
  
  <p>I know that it's not exactly true and you may use <code>git merge</code> if you are merging from 
  branch which was properly rebased on <em>master</em> prior merge, but I'm trying to make it safer and actually use <code>git format-patch</code> and <code>git am</code>. We are using code review, so I'm making patches anyway. I also knew about <code>git cherry-pick</code>, but I want to just <code>git am /reviewed/patches/dir/*</code> without actually recalling what commits was corresponding to this patches (without reading patches, that is).</p>
  
  <p>So, what's wrong with <code>git svn</code> and <code>git am</code>? It's simple - <code>git am</code> for a few very hard points is doing <em>CRLF</em> into <em>LF</em> conversion for patches supplied (<code>git-mailsplit</code> is doing this, to be precise), if not rebasing. <code>git format-patch</code> is also producing proper (LF-ended) patches.</p>
  
  <p>As my repo is mostly <em>CRLF</em> (and it should remain so), patches are, obviously, failing due to wrong EOL. Converting diffs to <em>CRLF</em> and somehow hacking <code>git am</code> to prevent it from conversion is not working, too. It will fail if any file was removed or deleted - <code>git apply</code> will complain about expected /dev/null (but he got <code>/dev/null^M</code>).</p>
  
  <p>And if I'm applying it with <code>git am --ignore-space-change --ignore-whitespace</code> that it will
  commit LF endings straight to the index, which is also weird. I don't know if it will preserve over commiting into svn (via <code>git svn dcommit</code>) and checking it out and I don't want to try out.</p>
  
  <p>Of course, it's still possible to try hacking around patches to convert only actual diffs, but this is too much hacks for simple task.</p>
  
  <p>So, I wonder, is there really no established way to produce patches and apply them to the same repo on the same system? It just feels weird that <em>msysgit</em> can't apply it's own patches.</p>