title: Branch/master tag revision increments using Git
body: <p>I'm trying to nail down a good system for release management, combined with the tagging practice of tagging with version numbers - for example, 1.0. Any changes after that tag will be incremented, like 1.0-1, 1.0-2, etc.</p>
  
  <p>However, if I create a new branch from master for 1.0 release, and then I switch to that branch and tag it 1.0, the system as mentioned above works fine. Additional bug fixes on that branch show as expected, 1.0-1, 1.0-2</p>
  
  <p>However, any work on the master, unless I re-tag the master after the first commit after making the 1.0 branch, will also show the same increment: 1.0-1, 1.0-2</p>
  
  <p>Granted, the sha1 hashes will be unique, but I'd end up having the same revisions/increments from both master and branch.</p>
  
  <p>Is there any way to avoid master from being tagged at all when I just tag the branches? Is there any better way of doing this? Right now, my only option after making branch 1.0 is make one minor commit on master, and then re-tag it for 1.1-dev or something.</p>
  
  <p>Then repeat for each release.</p>
  
  <p>However, if a branch is then tagged again, say for 1.0.1 release, that too seems like it would also tag master since that's what happened first?</p>