# HG changeset patch # User FUJIWARA Katsunori # Date 2012-04-22 15:30:45 # Node ID 8436a4e21417fbc05fd34aa787f5177b9ae99cf9 # Parent 0b463f52b948a52c53bcb4bd5d5f83c75796f451 doc: fix careless document miss in help of hgext/notify according to configuration example below, and direction of changeset transference, this paragraph should describe about "changegroup" hook. [hooks] # one email for each incoming changeset incoming.notify = python:hgext.notify.hook # one email for all incoming changesets changegroup.notify = python:hgext.notify.hook # one email for all outgoing changesets outgoing.notify = python:hgext.notify.hook diff --git a/hgext/notify.py b/hgext/notify.py --- a/hgext/notify.py +++ b/hgext/notify.py @@ -11,7 +11,7 @@ This extension let you run hooks sending changesets are being pushed, from the sending or receiving side. First, enable the extension as explained in :hg:`help extensions`, and -register the hook you want to run. ``incoming`` and ``outgoing`` hooks +register the hook you want to run. ``incoming`` and ``changegroup`` hooks are run by the changesets receiver while the ``outgoing`` one is for the sender:: diff --git a/tests/test-notify.t b/tests/test-notify.t --- a/tests/test-notify.t +++ b/tests/test-notify.t @@ -23,7 +23,7 @@ are being pushed, from the sending or receiving side. First, enable the extension as explained in "hg help extensions", and register - the hook you want to run. "incoming" and "outgoing" hooks are run by the + the hook you want to run. "incoming" and "changegroup" hooks are run by the changesets receiver while the "outgoing" one is for the sender: [hooks]