Emailing changes automatically
I would like to automatically send to the Gambit mailing list all the changes that are made to the Gambit repository. I tried following the instructions in: http://morecode.wordpress.com/2007/08/03/setting-up-mercurial-to-e- mail-on-a-commit/ but that doesn't seem to work. Does anyone here have experience with doing that? The .hg/hgrc file I'm using is attached below. Marc [paths] default-push = ssh://gambit@trex.iro.umontreal.ca/HTML/repo/gambit default = http://www.iro.umontreal.ca/~gambit/repo/gambit/ [extensions] hgext.notify = [hooks] # batch emails when many changesets incoming at one time changegroup.notify = python:hgext.notify.hook [smtp] host = localhost [email] from = gambit@iro.umontreal.ca [web] baseurl = http://www.iro.umontreal.ca/~gambit/repo/gambit/ [notify] # config items go in here config = /part/02/www-perso/usagers/gambit/HTML/repo/notify.conf maxdiff = 0 # max lines of diffs to include (0=none, -1=all) maxsubject = 67 # truncate subject line longer than this diffstat = False # add a diffstat before the diff content sources = serve push pull bundle # notify if source of incoming changes in this\ list # 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 Note that the file /part/02/www-perso/usagers/gambit/HTML/repo/ notify.conf contains: [reposubs] # key is glob pattern, value is ","-separated list of subscriber emails * = feeley@iro.umontreal.ca # [usersubs] # # key is subscriber email, value is ","-separated list of glob patterns # user@host = pattern # # [reposubs] # # key is glob pattern, value is ","-separated list of subscriber emails # pattern = user@host
Afficher les réponses par date
On 9/12/07, Marc Feeley <feeley@iro.umontreal.ca> wrote:
I would like to automatically send to the Gambit mailing list all the changes that are made to the Gambit repository.
Well if you commit anything like as frequently as I do, that will quickly overwhelm the list. Would it make more sense to have a separate parallel list for this? david -- Once you label me, you negate me - Soren Kierkegaard
On Sep 12, 2007, at 2:29 PM, David Rush wrote:
On 9/12/07, Marc Feeley <feeley@iro.umontreal.ca> wrote:
I would like to automatically send to the Gambit mailing list all the changes that are made to the Gambit repository.
Well if you commit anything like as frequently as I do, that will quickly overwhelm the list. Would it make more sense to have a separate parallel list for this?
Marc made an average of exactly 1 commit a day over the past two weeks; that doesn't seem too much, even if the pace is doubled after people start suggesting patches. This isn't gcc, which has a separate list for checkins, where there were 46 commits yesterday. gcc has separate lists for general discussions (gcc), help (gcc- help), discussion of patches, which also serves as a record of which patches are committed (gcc-patches), and an automatic record of commits to their svn repository (gcc-cvs, which tells you what their previous content management system was ;-). I suggest we see what happens for a while with a single list. Brad
participants (3)
-
Bradley Lucier -
David Rush -
Marc Feeley