Evolve & Tagging
Sebastian Unger
sebunger44 at gmail.com
Tue May 10 19:16:33 UTC 2016
On May 11, 2016 12:45 AM, "Sébastien Gautrin" <sebastien.gautrin at gmail.com>
wrote:
> Considering the purpose of evolve, the “natural” expectation would be
that after evolving the code base the affected tag point to the replacement
target (option 3.5.1 in the list).
I strongly disagree here! A tag is supposed to mark a particular state of
the code base for instance associated with a release. That state must be
immutable.
Why not simply make the tagged change sets public as part of the tag
command? That should not affect any workflows out there and would achieve
making the target of the tag immutable.
Cheers,
Seb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-evolve-testers/attachments/20160511/b21144ee/attachment-0002.html>
More information about the Evolve-testers
mailing list