Tagging a commit on different branch creates commit on current branch
I tagged commit x on branch A. When I then set to push the new commit, y, I was completely confused. I do not master Mercurial, but it took me several minutes to realize that TortoiseHg had created y on a branch different from x's, B, because my working set was on branch B.
When asked to tag a commit on a different branch, TortoiseHg should either:
- refuse
- create the new commit (y) on the branch of the tagged commit (x)
- ...or ask what to do
This affects 6.4.2.