title: git cherry-pick succeeds but shows worktree as dirty due to eol mismatch
body: <p>I am trying to cherry-pick a change from another branch under Windows. The change creates a subdirectory and some files. While the command itself completes successfully, <code>git status</code> reports all new files as changed. <code>git diff</code> indicates a change in every line, but <code>git diff -w</code> comes out empty, indicating an EOL issue. Here are more details:</p>
  
  <pre><code>$ git reset --hard 6e9f9af
  HEAD is now at 6e9f9af Hashing helper
  $ git status
  On branch newmaster
  nothing to commit, working directory clean
  $ git cherry-pick -m 1 5bd71b0
  [newmaster d36aba2] &lt;comment&gt;
   Date: Sun Mar 27 19:21:35 2016 -0700
   37 files changed, 2552 insertions(+)
   create mode 100644 src/phserver/winservice/Config.cpp
   . . . 
  $ git status
  On branch newmaster
  Changes not staged for commit:
    (use "git add &lt;file&gt;..." to update what will be committed)
    (use "git checkout -- &lt;file&gt;..." to discard changes in working directory)
  
          modified:   winservice/Config.cpp
   . . .
  </code></pre>
  
  <p>What did not help:</p>
  
  <ul>
  <li>Setting repo's <code>core.autocrlf</code> to either <code>true</code>, <code>false</code> or <code>input</code> before the cherry-pick. This is interesting, as the files are new and not in the index before the command. Looks like I speak less Git than I thought...</li>
  <li>Attempting both Git for Windows 2.6.2 and Cygwin git 2.5.3.</li>
  <li>Using <code>git cherry-pick -Xignore-all-space</code></li>
  <li><p>Modifying the cherry-pick commit. This worked <em>to a degree</em>:</p>
  
  <pre><code>$ git cherry-pick -m 1 5bd71b0 -Xignore-all-space -n
  $ git add -u .
  $ git commit
  </code></pre>
  
  <p>While that left the worktree clean, next cherry-picked patch failed horrifically due to eol mismatches--looks like this does not solve the issue in general, and only applicable when all files in the source commit are new.</p></li>
  </ul>
  
  <p>I would appreciate suggestions, and, better yet, an explanation as to what is really going on.</p>