Mercurial Mercurial > mercurial / diff
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset | file | latest | revisions | annotate | diff | comparison | raw | help
Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
tests/test-notify.out
changeset 9068 27a41250a9ce
parent 8935 f4f0e902b750
child 9104 c9c5aa12a46e 
--- 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
mercurial