[PATCH 2 of 2] releasenotes: add custom admonitions support for release notes

[Kevin Bullock]

> On Jul 3, 2017, at 08:17, Yuya Nishihara <yuya at tcha.org> wrote:
> 
> On Sat, 1 Jul 2017 00:10:50 +0530, Pulkit Goyal wrote:
>> On Fri, Jun 30, 2017 at 4:27 AM, Rishabh Madan <rishabhmadan96 at gmail.com> wrote:
>>> # HG changeset patch
>>> # User Rishabh Madan <rishabhmadan96 at gmail.com>
>>> # Date 1498776526 -7200
>>> #      Fri Jun 30 00:48:46 2017 +0200
>>> # Node ID 9674e42ec8aac0f4f0d237c6270b38ace21d5d52
>>> # Parent  9f7c675413ffce1497c7db3ff1495e4050b151d6
>>> releasenotes: add custom admonitions support for release notes
>>> 

[...]

>> Can we name this more extension specific like [releasenotes.sections]
>> or something similar. Also the custom sections should override default
>> sections. For example, someone might like to expand api to be
>> something different or bc to something different.
> 
> Maybe this isn't a per-user thing, but tied with a repository (like .hgtag
> or .hgeol) ?

Rishabh and I had discussed this a bit on IRC, and I noted that e.g. the keyword extension keeps custom keyword settings in the hgrc. So I'm not sure whether this should be per-repo or per-user, but my first instinct was the same as yours: that it should travel along with the repo.

If it does land in config, then per-project settings could always be %include'd into the repo's .hg/hgrc.

pacem in terris / мир / शान्ति / ‎‫سَلاَم‬ / 平和
Kevin R. Bullock