# HG changeset patch
# User Martin Geisler <mg@lazybytes.net>
# Date 2009-07-25 23:55:18
# Node ID 0efb3360bdb32876816c6b88d63660e96f2fa77c
# Parent  39426716a07e47b12000ae855ddb3aaeea49fe8b

notify: wrap docstrings at 70 characters

diff --git a/hgext/notify.py b/hgext/notify.py
--- a/hgext/notify.py
+++ b/hgext/notify.py
@@ -7,10 +7,11 @@
 
 '''hooks for sending email notifications at commit/push time
 
-Subscriptions can be managed through a hgrc file. Default mode is to print
-messages to stdout, for testing and configuring.
+Subscriptions can be managed through a hgrc file. Default mode is to
+print messages to stdout, for testing and configuring.
 
-To use, configure the notify extension and enable it in hgrc like this::
+To use, configure the notify extension and enable it in hgrc like
+this::
 
   [extensions]
   hgext.notify =
@@ -47,8 +48,9 @@ Optional configuration items::
   [web]
   baseurl = http://hgserver/... # root of hg web site for browsing commits
 
-The notify config file has same format as a regular hgrc file. It has two
-sections so you can express subscriptions in whatever way is handier for you.
+The notify config file has same format as a regular hgrc file. It has
+two sections so you can express subscriptions in whatever way is
+handier for you.
 
 ::
 
@@ -62,8 +64,8 @@ sections so you can express subscription
 
 Glob patterns are matched against path to repository root.
 
-If you like, you can put notify config file in repository that users can push
-changes to, they can manage their own subscriptions.
+If you like, you can put notify config file in repository that users
+can push changes to, they can manage their own subscriptions.
 '''
 
 from mercurial.i18n import _