[issue318] Default behaviour of "hg tag" is surprising

[Bryan O'Sullivan]

New submission from Bryan O'Sullivan <bos at serpentine.com>:

I ran "hg tag foo" today with my working directory set to a non-tip revision,
and was surprised that tip was tagged, not the parent of the working directory.
 Even though this behaviour is documented, I don't think it makes any sense. 
For example, a way I'd expect to use it is as follows:

- update to some rev
- test it
- tag it

Since tip gets tagged by default, I have to either remember which rev I updated
to or run "hg parents" to find it, which is both surprising and unnecessary.

I'd suggest that if the working dir has one parent, that
tag-without-explicit-rev should tag that parent.  If two parents, tag should
require an explicit rev to tag against.

----------
messages: 1711
nosy: bos
priority: bug
status: unread
title: Default behaviour of "hg tag" is surprising

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