Mercurial > hg

changeset 16500:8436a4e21417 stable

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
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
author FUJIWARA Katsunori <foozy@lares.dti.ne.jp>
date Mon, 23 Apr 2012 00:30:45 +0900
parents 0b463f52b948
children 340d047ea577
files hgext/notify.py tests/test-notify.t
diffstat 2 files changed, 2 insertions(+), 2 deletions(-) [+]
line wrap: on
line diff
--- a/hgext/notify.py	Mon Apr 23 00:29:04 2012 +0900
+++ b/hgext/notify.py	Mon Apr 23 00:30:45 2012 +0900
@@ -11,7 +11,7 @@
 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::
 
--- a/tests/test-notify.t	Mon Apr 23 00:29:04 2012 +0900
+++ b/tests/test-notify.t	Mon Apr 23 00:30:45 2012 +0900
@@ -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]