[Bug 5775] New: relnotes extension choked on two revisions in the 4.5 development cycle
mercurial-bugs at mercurial-scm.org
mercurial-bugs at mercurial-scm.org
Mon Jan 22 23:29:08 UTC 2018
https://bz.mercurial-scm.org/show_bug.cgi?id=5775
Bug ID: 5775
Summary: relnotes extension choked on two revisions in the 4.5
development cycle
Product: Mercurial
Version: default branch
Hardware: PC
OS: Mac OS
Status: UNCONFIRMED
Severity: feature
Priority: wish
Component: Mercurial
Assignee: bugzilla at mercurial-scm.org
Reporter: durin42 at gmail.com
CC: mercurial-devel at mercurial-scm.org
da91e7309daf8ffc51bf3e6f4b2d8a16ef5af95a and
3398603c5621b52dcd6b4c31444635a6979d561d both break the relnotes extension hard
enough it gave up on giving me release notes and I had to exclude them. Two
things come to mind:
1) The abort should mention which changeset caused problems when it gives up
2) We should try to do better about not giving up
For bonus points, we could add a hasrelnotes() revset so that revisions with no
relnotes can be selected for later analysis? I'm not sure if that's a good idea
tho.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Mercurial-devel
mailing list