D447: templatekw: choose {latesttag} by len(changes), not date (issue5659)

Sean Farley sean at farley.io
Fri Aug 18 17:11:17 EDT 2017


martinvonz (Martin von Zweigbergk) <phabricator at mercurial-scm.org> writes:

> martinvonz created this revision.
> Herald added a subscriber: mercurial-devel.
> Herald added a reviewer: hg-reviewers.
>
> REVISION SUMMARY
>   As Augie reported in the bug, the current heuristic of choosing the
>   best tag of a merge commit by taking the one with newest tag (in terms
>   of tagging date) currently fails in the Mercurial repo itself. Copying
>   the example from Yuya:

Ah, great! I was working on this same bug because my ppa script kept
failing due to the wrong tag being used. Using the min(changesets) with
tie-breaker as the date was the exact route I was going to go. So,
thanks for saving me the trouble :-)

Queued for stable (It seems that information was lost in phabricator?
Thanks to Martin for letting me know on IRC)!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 800 bytes
Desc: not available
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20170818/410d8072/attachment.sig>


More information about the Mercurial-devel mailing list