title: Long term support using git-flow to merge a hotfix to develop branched off the support branch
body: <p>Doing experimental learning of git flow for my new project.. I noticed the following:</p>
  
  <p>The following scenarios: </p>
  
  <ol>
  <li><p>Normally git-flow workings:</p>
  
  <p><code>git flow hotfix start 1.1.2</code></p>
  
  <p>Will create a branch based on master and when done merges with master and develop. </p></li>
  <li><p>Branching based on another branch</p>
  
  <p><code>git flow hotfix start 1.1.3 support/1.x</code></p>
  
  <p>But then the hotfix created based on support branch will merge back into that support branch and not back into develop nor master but will be tagged when finished.</p></li>
  </ol>
  
  <p><strong>Problem</strong></p>
  
  <p>If my master branch is currently in <code>v3.2.0</code> but the hotfix was for an issue in a code section introduced in <code>v1.1</code> but still relevant and used in the current development branch, how do I go about merging them together?</p>
  
  <p>The reason for this question is that some clients would need long term support of a specific older version even if your newer version is more superior.</p>
  
  <p><strong>Possibly solution but not( using SourceTree)</strong></p>
  
  <p>Atlassian SourceTree always only merge finish hotfix with master and develop but never with the support branch that is needed by clients <strong><em>(tested thrice)</em></strong></p>