Evolve & Tagging
Pierre-Yves David
pierre-yves.david at ens-lyon.org
Tue May 10 13:35:35 UTC 2016
On 05/10/2016 02:45 PM, Sébastien Gautrin wrote:
> On 10/05/16 14:36, David Douard wrote:
>
>> in which the proposed solution it listed as point 3.5.6. I know Matt
>> really is conservative about bw compat breakages, but I really think
>> it's the best solution in this list. My 2c
>
> Considering the issue is related to evolve, affecting the behaviour of
> a non-evolve command in such a way would not seem a good idea to me.
> 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).
(small note) This is not evolve specific, someone can get into the same
issue right now use hg tag and histedit.
--
Pierre-Yves David
More information about the Evolve-testers
mailing list