Evolve & Tagging
David Douard
david.douard at logilab.fr
Tue May 10 12:36:27 UTC 2016
On 05/10/2016 02:11 PM, Pierre-Yves David wrote:
> On 05/10/2016 12:46 PM, Sebastian Unger wrote:
>> Hi,
>>
>> Just an observation: The tag command should probably refuse to tag a non-public changeset. This isn't strictly evolve related, but it only becomes a big issue with evolve work flows.
>
> Tagging + draft is clearly an issue, however the correct approach to take is unclear and the problem still need to be tackled. There is multiple ideas flying around. I've written a short summary of them on the wiki:
>
> https://www.mercurial-scm.org/wiki/ChangesetEvolutionDevel#Tagging_draft_changeset
>
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
> Cheers
>
--
David DOUARD LOGILAB
Directeur du département Outils & Systèmes
+33 1 45 32 03 12 david.douard at logilab.fr
http://www.logilab.fr/id/david.douard
Formations - http://www.logilab.fr/formations
Développements - http://www.logilab.fr/services
Gestion de connaissances - http://www.cubicweb.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: david_douard.vcf
Type: text/x-vcard
Size: 302 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-evolve-testers/attachments/20160510/28503882/attachment-0002.vcf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-evolve-testers/attachments/20160510/28503882/attachment.asc>
More information about the Evolve-testers
mailing list