notify extension help

Neal Becker ndbecker2 at gmail.com
Tue Jun 9 13:12:58 CDT 2009


I'm trying to setup notify.  I'm not getting mail.  I wonder if it's because 
I'm checking in directly on local FS, not via push, pull, etc.  AFAICT, 
sources can be [serve push pull bundle], but that doesn't sound like it 
covers local fs checkin.

Running a test checkin does nothing:
hg ci -m 'test notify' --debug
hdl/demod/step1/verilog/rtl/step1.v
committed changeset 868:4832280a7382207858224c493f0a7856c6595496

I hoped --debug would turn on debug within notify.py, but it didn't.

Here's what I have:

[paths]
default = /home/nbecker/scma-ldpc-fixed

[extensions]
hgext.notify = 

[hooks]
# Enable either changegroup or incoming.
# changegroup will send one email for each push,
# whereas incoming sends one email per changeset.
# Note: Configuring both is possible, but probably not
#       what you want, you'll get one email for the group
#       and one for each changeset in the group.
changegroup.notify = python:hgext.notify.hook
#incoming.notify = python:hgext.notify.hook

[email]
from = ndbecker2 at gmail.com

[smtp]
host = localhost
# Optional options:
# username = joeuser
# password = secret
# port = 25
# tls = true
# local_hostname = me.example.com

# presently it is necessary to specify the baseurl for the notify
# extension to work.  It can be a dummy value if your repo isn't
# available via http
[web]
baseurl = http://nbecker6:8082

[notify]
# multiple sources can be specified as a whitespace separated list
sources = serve push pull bundle
# set this to False when you're ready for mail to start sending
test = True
# While the subscription information can be included in this file,
#   (in which case, set: config =)
# having it in a separate file allows for it to be version controlled
# and for the option of having subscribers maintain it themselves.
config = 
# you can override the changeset template here, if you want.
# If it doesn't start with \n it may confuse the email parser.
# here's an example that makes the changeset template look more like hg log:
#template = \ndetails:   {baseurl}{webroot}/rev/{node|short}\nchangeset: 
{rev}:{node|short}\nuser:      {author}\ndate:      {date|
date}\ndescription:\n{desc}\n
# max lines of diffs to include (0=none, -1=all)
maxdiff = 300

#[usersubs]
## key is subscriber email, value is comma-separated list of glob patterns
#yourproject-hg at lists.berlios.de = **

[reposubs]
# key is glob pattern, value is comma-separated list of subscriber emails
** = someone at somewhere...




More information about the Mercurial mailing list