"Nicholas A. Bellinger" [off-list ref] writes:
22:33 < warthog9> not use the same name, I think what your doing is fine just the identical naming is whats
causing the problem
22:33 < warthog9> like tag-lio-3.0
22:33 < nab> Ahhhhhh
22:33 < warthog9> and branch: lio-3.0
22:34 < warthog9> since I think somewhere in git it's got two different orders of preference for tag vs. branch
I do not speak for gitweb but we typically favor tags over heads. The
only place "branch name" take precedence is where the command expects to
see a name of a branch, when it can also take any arbitrary object name,
and changes behaviour. I.e. "git checkout X", when X is a branch name,
checks out the branch so that the next commit advances the tip of that
branch.