title: confused about creating nested branches in git
body: <p>I just started using git and started collaborating with other developers on same code. I have worked a little with SVN before but never had to collaborate with other people on my codebase. 
  Now with collaborators working on same code, I need an efficient workflow. While searching for such, I found <a href="http://nvie.com/posts/a-successful-git-branching-model/" rel="noreferrer">this</a>, and it seems like a good workflow for our requirement.</p>
  
  <p>My repository resides in a local machine. I created the repository with <code>git init --bare</code>.  I added the initial codes to master and pushed it. Then I added a "develop" branch using <code>git branch develop; git push -u origin develop</code>.</p>
  
  <p>Now I want to create feature branches from "develop", and I want these feature branches to be accessible by all collaborators. I wish to have a nested structure, something like this</p>
  
  <pre><code>origin/master
  origin/develop
  origin/develop/newFeature
  origin/develop/anotherFeature
  etc.
  </code></pre>
  
  <p>so that when a collaborator types in <code>git branch -a</code> he/she will immediately know the "newFeature" is in the "develop" line, and decides what to do.</p>
  
  <p>So after some trial and error, this is what I did:</p>
  
  <pre><code>git clone file:///path/to/repo --branch develop
  git checkout -b newFeature develop
  EDIT some files
  git add .
  git commit
  git push origin newFeature
  </code></pre>
  
  <p>Now this "newFeature" is available for all collaborator to clone. <code>git branch -a</code> gives me</p>
  
  <pre><code>  develop
  * newFeature
    remotes/origin/HEAD -&gt; origin/master
    remotes/origin/develop
    remotes/origin/master
    remotes/origin/newFeature
  </code></pre>
  
  <p>So is the "newFeature" really part of the "develop" branch? Or is it now branch by itself? Once I clone the "newFeature", how do I check whether it is the develop line? This may potentially be confusing as I may end up having a branch named "newFeature" in master in due time! </p>
  
  <p>My understanding of how git works is definitely inadequate. Therefore, if anyone can point me to right direction, that will be great!</p>
  
  <p>TIA,</p>