title: Understanding graphical representation of Git Extensions Branches
body: <p>Coming from SVN, I am still getting used to the complexity of Git.  Having discovered first hand that TortoiseGit is just asking for trouble, I am also discovering Git Extensions.  </p>
  
  <p>As I have done in the past, I managed to work on three separate tasks before finishing any of them--not so wise, I know.  It lets me practice branching though, that's for sure.  </p>
  
  <p>I now have three branches in addition to <code>master</code>: <code>thread-safe</code>, <code>common-create-web-request</code> and <code>change-alias-target</code>.  At this point, nothing is unstaged, all changes are committed to one of those three branches (or so I thought, see next paragraph) and none of them has been pushed or merged.</p>
  
  <p>I am just curious, and a little concerned, that the Git Extensions Browse window seems to show graphically that, although the revisions to the branches <code>thread-safe</code> and <code>common-create-web-request</code> are on those branches, the two revisions to the branch <code>change-alias-target</code> are not (I am looking at the graph running up the left side of the list of revisions).  If I mistakenly committed them to.. <code>master</code>? then I guess I need to know how to move them to the branch <code>change-alias-target</code>, please.</p>
  
  <p><a href="https://i.stack.imgur.com/hO1Hy.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/hO1Hy.png" alt="enter image description here"></a></p>