Mercurial > hg
changeset 9266:0efb3360bdb3
notify: wrap docstrings at 70 characters
| author | Martin Geisler <mg@lazybytes.net> |
|---|---|
| date | Sun, 26 Jul 2009 01:55:18 +0200 |
| parents | 39426716a07e |
| children | bd9e5d200186 |
| files | hgext/notify.py |
| diffstat | 1 files changed, 9 insertions(+), 7 deletions(-) [+] |
line wrap: on
line diff
--- a/hgext/notify.py Sun Jul 26 01:53:49 2009 +0200 +++ b/hgext/notify.py Sun Jul 26 01:55:18 2009 +0200 @@ -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 @@ [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 @@ 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 _