# HG changeset patch # User Martin Geisler # Date 1247003682 -7200 # Node ID 27a41250a9ce711678e8c8ead81cf6b07794a95e # Parent 2ebac2bf7ad5c063ed43121181ff9f32d3369e33 notify: wrapped docstrings at 78 characters diff -r 2ebac2bf7ad5 -r 27a41250a9ce hgext/notify.py --- a/hgext/notify.py Tue Jul 07 23:54:42 2009 +0200 +++ b/hgext/notify.py Tue Jul 07 23:54:42 2009 +0200 @@ -7,8 +7,8 @@ '''hooks for sending email notifications at commit/push time -Subscriptions can be managed through hgrc. Default mode is to print -messages to stdout, for testing and configuring. +Subscriptions can be managed through hgrc. Default mode is to print messages +to stdout, for testing and configuring. To use, configure notify extension and enable in hgrc like this: @@ -47,9 +47,8 @@ [web] baseurl = http://hgserver/... # root of hg web site for browsing commits - notify config file has same format as regular hgrc. it has two - sections so you can express subscriptions in whatever way is handier - for you. + notify config file has same format as regular hgrc. it has two sections so + you can express subscriptions in whatever way is handier for you. [usersubs] # key is subscriber email, value is ","-separated list of glob patterns @@ -61,8 +60,9 @@ 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 _ from mercurial import patch, cmdutil, templater, util, mail diff -r 2ebac2bf7ad5 -r 27a41250a9ce tests/test-notify.out --- a/tests/test-notify.out Tue Jul 07 23:54:42 2009 +0200 +++ b/tests/test-notify.out Tue Jul 07 23:54:42 2009 +0200 @@ -1,7 +1,7 @@ notify extension - hooks for sending email notifications at commit/push time -Subscriptions can be managed through hgrc. Default mode is to print -messages to stdout, for testing and configuring. +Subscriptions can be managed through hgrc. Default mode is to print messages +to stdout, for testing and configuring. To use, configure notify extension and enable in hgrc like this: @@ -40,9 +40,8 @@ [web] baseurl = http://hgserver/... # root of hg web site for browsing commits - notify config file has same format as regular hgrc. it has two - sections so you can express subscriptions in whatever way is handier - for you. + notify config file has same format as regular hgrc. it has two sections so + you can express subscriptions in whatever way is handier for you. [usersubs] # key is subscriber email, value is ","-separated list of glob patterns @@ -54,8 +53,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. no commands defined % commit