Manually adding tags

[Becker, Mischa J]

-----Original Message-----
From: mercurial-bounces at selenic.com [mailto:mercurial-bounces at selenic.com] On Behalf Of Scott Palmer
Sent: Friday, August 26, 2011 6:42 AM
To: mercurial
Subject: Re: Manually adding tags

> On 2011-08-26, at 8:40 AM, Isaac Jurado wrote:
>
>> On Fri, Aug 26, 2011 at 1:26 PM, Scott Palmer <swpalmer at gmail.com> wrote:
>>>
>>>> If I understood correctly, you wan to tag a changeset you are about
>>>> to commit, right?  If that is the case, you can forget about it
>>>> because the .hgtags file needs the revision ID (the SHA) which you
>>>> can't know until AFTER commit has been done.  So there is a
>>>> bootstrapping problem.
>>>>
>>>> Besides, the "hg tag" command is just that:
>>>>
>>>> $ echo "version shaid" >>.hgtags && hg commit
>>>
>>> I think he just wants to include more in that same commit. He is still
>>> tagging an older version.
>>
>> Oh well, in that case what I wrote doesn't apply.
>
> Now that I think about it, wouldn't it make sense to have something like
> a --no-commit option for hg tag ?
> That way we avoid people directly mucking about in the .hgtags file.  That
> could possible avoid some of the things that Greg was warning about
> earlier in this thread.

A no-commit option would be great.  Back when I used tags, I was always doing a rollback after the tag to undo the tag-only commit.  Since rollback leaves the .hgtags file altered, the new tag would be included in my next commit.

Mischa Becker

This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information that is confidential and protected by law from unauthorized disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.