Trouble Setting up email notifications

[Matt Mackall]

On Wed, 2011-08-24 at 12:56 -0400, charlie at thegallos.com wrote:
> Hi Gang,
> OK - stupid user questions here - I guess I don't really understand Hg
> 
> We're looking to add email notifications when our developers push up a
> changeset to the server - which is really just a common share among all of
> us
> 
> I've taken one sample repository (let's call it "MySample") and created a
> .hgrc file in it's .hg directory

.hg/hgrc <- correct
.hg/.hgrc <- incorrect

> I make an edit to my local repository (which was last cloned BEFORE the
> .hgrc file was created) , and then sync and push it back up, and guess
> what - No emails
> 
> Below is a sightly obfuscated version of the contents of the .hgrc (aka
> emails changed, servername changed)
> 
> If it makes any difference, the server is an exchange server that DOES
> have the smtp open
> 
> HELP
> 
> */////// begin file /////*
> 
> [extensions]
> hgext.notify=
> 
> [hooks]
> changegroup.notify = python:hgext.notify.hook
> 
> [email]
> from = MyEmail at OurDomain.com
> 
> [smtp]
> host = OurSMTPServerName
> 
> # the baseurl is used for constructing hgweb-URLs for the mails
> # It can be a dummy value if your repo isn't
> # available via http
> 
> [web]
> baseurl = http://hgserver/...
> 
> [notify]
> # multiple sources can be specified as a whitespace separated list. The
> most common use case is for email to be sent if a push is made to the
> repository. This is corresponds to the sources keyword "serve", which is
> not obvious. What each of these keywords means really needs to be
> documented. Presumably an email will be sent if an action corresponding to
> any of the listed keywords is performed.
> sources = serve push pull bundle
> template = \nChange: {rev}:{node|short} in {webroot}\nAuthor:
> {author}\nDate: {date|date}\nDetails: {baseurl}{webroot}/rev/{node\
> |short}\nSummary:\n\n{desc}\n
> maxdiff = 0
> strip = 5
> 
> # set this to False when you're ready for mail to start sending
> test = False
> 
> # 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 = /path/to/subscription/file
> config =
> 
> [usersubs]
> ## key is subscriber email, value is comma-separated list of glob patterns
> MyTester at OurDomain.com = **, MyEmail at OurDomain.com = **
> 
> 
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial


-- 
Mathematics is the supreme nostalgia of our time.