title: Gitflow: Merging release bugfixes back to develop from master
body: <p>My question is around a very specific point in the gitflow process (as documented <a href="http://nvie.com/posts/a-successful-git-branching-model/#finishing-a-release-branch" rel="nofollow noreferrer">here</a>).</p>
  
  <p>I've already merged bugfixes from <code>release/1.2</code> into <code>master</code>, and tagged appropriately.</p>
  
  <p>Apart from how the history looks, what are differences between back-merging from <code>release/1.2</code> vs back-merging from <code>master</code> into <code>develop</code>.</p>
  
  <p>I have tried both ways, and in my simple, contrived example I see no difference in <code>develop</code>, as I expected.</p>
  
  <p>Are there dangers to this? Am I going to encounter messy issues later on? Am I missing something obvious? I suspect the answer may be to do with other features that have gone into <code>master</code>, but which should remain out of <code>develop</code> for the moment.</p>
  
  <p><strong>merging release in to develop:</strong></p>
  
  <p><a href="https://i.stack.imgur.com/RKBmR.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/RKBmR.png" alt="enter image description here"></a></p>
  
  <p><strong>merging master in to develop:</strong></p>
  
  <p><a href="https://i.stack.imgur.com/khV9P.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/khV9P.png" alt="enter image description here"></a></p>