[issue2207] Allow the notify extension configuration file to contain all the configuration fields (including the sources, template, maxdiff, etc)

didlybom bugs at mercurial.selenic.com
Fri May 21 09:36:40 UTC 2010


New submission from didlybom <didlybom at gmail.com>:

Currently the notify extension configuration is split between the
mercurial.ini (or .hgrc) file and the "config" file, whose path is set via
the "config" option of the notify section of the mercurial.ini.

In order to easily share a common notify extension configuration among
several users who have access to a shared network folder, it would be great
if the whole notify extension configuration could be moved into the "config
file".

In this way, all that every user would need to do to configure their machine
to use the common team notification would be to add the config file location
to the notify section of their mercurial.ini file.

Ideally the user should be able to override any of the config settings
specified in the config file by setting the same setting in their
mercurial.ini file. That is, the settings set on the config file would be
used as default values which could be overriden by the user by simply
setting them on their mercurial.ini.

These changes would make using the notify extension on a non-server based
mercurial configuration much more convenient. Basically the notify config
file could be set to notify on push using a certain template. Then everybody
would point to that shared config file and then whenever they performed a
push to any shared repository all the users subscribed to that respository
via the [usersubs] or [reposubs] sections of the config file would get the
corresponding notification.

----------
messages: 12618
nosy: didlybom
priority: feature
status: unread
title: Allow the notify extension configuration file to contain all the configuration fields (including the sources, template, maxdiff, etc)
topic: notify

____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue2207>
____________________________________________________


More information about the Mercurial-devel mailing list