Stamps

[Didly]

On Mon, May 9, 2011 at 8:34 PM, Kevin Bullock
<kbullock+mercurial at ringworld.org> wrote:
> On May 7, 2011, at 6:52 PM, Adrian Buehlmann wrote:
>
>> veracity [1] has the concept of "stamps". A stamp is like a tag (a name)
>> that can be applied to changesets. But a stamp differs from a tag
>> because the same stamp can be applied to *multiple* changesets.
>>
>> Example usage: "passes test", "behavior change", "pending review"
>>
>> I think this could be an interesting notion. So we might steal the idea.
>>
>> Seeing recent discussions about new states and such, I thought I'll
>> throw this in the ring.
>>
>> [1] http://www.sourcegear.com/veracity/
>
> Actually, you could do this with no code at all: keep a plain-text log in your repo that records the list of changesets for a stamp, one log file per stamp. Have your build system append to it and auto-commit when it successfully runs a build. Then the stamp log is dual-purpose: it lets you see the list of (e.g.) successful builds without even consulting `hg log`.
>
> pacem in terris / mir / shanti / salaam / heiwa
> Kevin R. Bullock
>
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel
>

An additional difference between stamps and branches is that a
changeset cannot belong to a single branch, while a chanset could
potentially have multiple stamps.

Angel