Bookmarks in core?

[Kevin Bullock]

On Dec 8, 2010, at 4:02 AM, Martin Geisler wrote:

> Adrian Buehlmann <adrian at cadifra.com> writes:
> 
>> On 2010-12-06 12:44, Didly Bom wrote:
>> 
>>> "Why does creating a tag create a newcommit??":
>> 
>> Because it changes a project and it is an integral part of "what
>> happened" in the history of a project. There ain't no such thing as a
>> separate history for anything in a specific project.
> 
> No, no, making a tag does not change the project -- the project stays
> the same no matter what name you attach to it. I think of tags as
> meta-datajust

Tagging doesn't change the _code_, but it absolutely does change the _project_. If I say I released v2.0 at this changeset, and later change the v2.0 tag to point to a different changeset, there had better be a record of that _in history_ (not that one should be changing release tags anyway!). Just as each changeset is a verifyable snapshot of the project, a tag is a verifyable statement about the _use_ of a particular snapshot. It's not "just metadata".

>  and expect them to behave as if I had made separate clones
> to keep track of things:
> 
>  hg clone . ../project-1.0
>  # hack, hack, hack...
>  hg clone . ../project-2.0

I can't count the number of open source developers I've had the urge to kneecap for not tagging their releases. The conceptual model you describe here is as bad as not tagging at all.

pacem in terris / mir / shanti / salaam / heiwa
Kevin R. Bullock