title: git - two branches named the same? Difference is one lower case - one mixed case?
body: <p>I am so used to typing in camelCase that I have been doing it in git.  That is - until I realized git is case sensitive!!   File names included.</p>
  
  <p>From history - at the start of this production branch - it was ClientMgr.    But just at the start.</p>
  
  <p>All the work past the initial commit - has been on branch - clientmgr.</p>
  
  <p>A few hours ago - I realized the problem.    Since the tree was straight - and not branches - I tried deleting ClientMgr.   Right after - I had 195 new files when before all was clean.</p>
  
  <p>Unsure - I restored a backup - but now have two branches - with the same name - different cases.    </p>
  
  <p>Do I continue on - and just ignore the ClientMgr?   Or is there a sane way to clean this up?    </p>
  
  <p>I would really love to end up with one.  I have some ideas - but tired at gitting shot it...</p>
  
  <p>Any and all suggestions appreciated.</p>
  
  <p>P.S. - guess this helps explain why I had some missing / lost changes a few days ago.</p>
  
  <p>I love git - hope to get past or mostly past the got-ya's
  +++++++++++++++++++++++
  Edit: 4/1/2013</p>
  
  <p>The ClientMgr was the original branch - with one commit.   I continued working (thinking I was on the ClientMgr branch but instead the new clientmgr branch.</p>
  
  <p>I am concerned because of the same name - different case I think is potential time bomb.  That is I suspect - git mostly treats them as separate - but not always.  For example - when on ClientMgr - and trying to check clientmgr - I get an error message that I am already on it.</p>
  
  <p>Seeing this - there could be other problems looming with this.</p>
  
  <p>I think my first step will be to backup again - and then try to rename ClientMgr to where there is not similarity - and test and see how that goes.</p>
  
  <p>It that goes well - at least I have (or may have) taken care of the </p>
  
  <p>Once again - I greatly appreciate everyone input.</p>
  
  <p>Jim H</p>
  
  <p>+++++++++++++++++++++++++
  Edit 2 </p>
  
  <p>Not what expected - but seems ok</p>
  
  <p>I renamed ClientMgr to oldclientmgr via
  git branch -m ClientMgr oldclientmgr</p>
  
  <p>Looking at the tree in SourceTree - it renamed both to oldclientmgr
  I checked the graph - and I looked to be where I wanted to be
  I opened and reviewed the code - and it look to be properly in place</p>
  
  <p>So as I thought - git is not always case sensitive - or it would not have renamed both branches.</p>
  
  <p>Once again - thank you!</p>
  
  <p>Jim H</p>