[issue1946] Disallow or at least WARN on creating a tag which conflicts with a branch name or vice versa

[Danny Sadinoff]

New submission from Danny Sadinoff <danny-mercurial at sadinoff.com>:

Tags with the same names as named branches can cause surprising (and possibly 
ill-defined)  behavior.  

In particular, it seems that if NAME is the name of both a tag and a branch, 
and I do an "hg up NAME", I get the tag, not the branch.  It's unclear from 
the documentation whether I should expect the branchy function or the taggy 
function, but either way, it could lead to commits on the wrong branches and 
thus much anguish.

I would suggest that it's an error to have tags with the same name as 
branches.  It ought to be prevented or at the very least warned about at 
tag/branch create time.

----------
messages: 11197
nosy: DannySadinoff
priority: wish
status: unread
title: Disallow or at least WARN on creating a tag which conflicts with a branch name or vice versa
topic: hg, named branches, tags

____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue1946>
____________________________________________________