title: Git merge "Already up-to-date" only when commits are the same
body: <p>This is the scenario: I have a develop branch from which I create new branches to add new features:</p>
  
  <pre><code>git checkout -b newfeature develop
  </code></pre>
  
  <p>After I completed the changes in newfeature, I checkout back to develop and try to merge the new changes (I use --no-ff because I want the merge to always create a commit object):</p>
  
  <pre><code>git checkout develop
  git merge --no-ff newfeature
  </code></pre>
  
  <p>And I get the following result: <code>Already up-to-date.</code>. I've read other questions at stackoverflow and I understand that this is not possible because <code>newfeature</code> is a parent of <code>develop</code>, but why develop has the changes of <code>newfeature</code> automatically without merging?</p>
  
  <p>Also, I tried to add a commit to <code>newfeature</code> and merged back to <code>develop</code>, and this time it worked; it created two commits on <code>develop</code> branch, one for merging and the other is the same as the commit of <code>newfeature</code>. </p>
  
  <p>I'm a little bit confused, could you guysclear my doubts?</p>