Mercurial > hg
changeset 7127:9df67ee30ef5
help: better documentation intro for a few extensions
author | Dirkjan Ochtman <dirkjan@ochtman.nl> |
---|---|
date | Sat, 18 Oct 2008 16:56:39 +0200 |
parents | 111813de4188 |
children | 2b8a2248312a |
files | hgext/churn.py hgext/highlight/__init__.py hgext/notify.py hgext/rebase.py tests/test-keyword.out |
diffstat | 5 files changed, 63 insertions(+), 64 deletions(-) [+] |
line wrap: on
line diff
--- a/hgext/churn.py Thu Jun 12 11:49:13 2008 +0200 +++ b/hgext/churn.py Sat Oct 18 16:56:39 2008 +0200 @@ -5,7 +5,7 @@ # # This software may be used and distributed according to the terms # of the GNU General Public License, incorporated herein by reference. -'''allow graphing the number of lines (or count of revisions) grouped by template''' +'''command to show certain statistics about revision history''' from mercurial.i18n import _ from mercurial import patch, cmdutil, util, templater
--- a/hgext/highlight/__init__.py Thu Jun 12 11:49:13 2008 +0200 +++ b/hgext/highlight/__init__.py Sat Oct 18 16:56:39 2008 +0200 @@ -1,4 +1,4 @@ -"""a mercurial extension for syntax highlighting in hgweb +"""syntax highlighting in hgweb, based on Pygments It depends on the pygments syntax highlighting library: http://pygments.org/
--- a/hgext/notify.py Thu Jun 12 11:49:13 2008 +0200 +++ b/hgext/notify.py Sat Oct 18 16:56:39 2008 +0200 @@ -4,66 +4,65 @@ # # This software may be used and distributed according to the terms # of the GNU General Public License, incorporated herein by reference. -# -# hook extension to email notifications to people when changesets are -# committed to a repo they subscribe to. -# -# default mode is to print messages to stdout, for testing and -# configuring. -# -# to use, configure notify extension and enable in hgrc like this: -# -# [extensions] -# hgext.notify = -# -# [hooks] -# # one email for each incoming changeset -# incoming.notify = python:hgext.notify.hook -# # batch emails when many changesets incoming at one time -# changegroup.notify = python:hgext.notify.hook -# -# [notify] -# # config items go in here -# -# config items: -# -# REQUIRED: -# config = /path/to/file # file containing subscriptions -# -# OPTIONAL: -# test = True # print messages to stdout for testing -# strip = 3 # number of slashes to strip for url paths -# domain = example.com # domain to use if committer missing domain -# style = ... # style file to use when formatting email -# template = ... # template to use when formatting email -# incoming = ... # template to use when run as incoming hook -# changegroup = ... # template when run as changegroup hook -# maxdiff = 300 # max lines of diffs to include (0=none, -1=all) -# maxsubject = 67 # truncate subject line longer than this -# diffstat = True # add a diffstat before the diff content -# sources = serve # notify if source of incoming changes in this list -# # (serve == ssh or http, push, pull, bundle) -# [email] -# from = user@host.com # email address to send as if none given -# [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. -# -# [usersubs] -# # key is subscriber email, value is ","-separated list of glob patterns -# user@host = pattern -# -# [reposubs] -# # key is glob pattern, value is ","-separated list of subscriber emails -# pattern = user@host -# -# glob patterns are matched against path to repo root. -# -# if you like, you can put notify config file in repo that users can -# push changes to, they can manage their own subscriptions. + +'''hook extension to email notifications on commits/pushes + +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: + + [extensions] + hgext.notify = + + [hooks] + # one email for each incoming changeset + incoming.notify = python:hgext.notify.hook + # batch emails when many changesets incoming at one time + changegroup.notify = python:hgext.notify.hook + + [notify] + # config items go in here + + config items: + + REQUIRED: + config = /path/to/file # file containing subscriptions + + OPTIONAL: + test = True # print messages to stdout for testing + strip = 3 # number of slashes to strip for url paths + domain = example.com # domain to use if committer missing domain + style = ... # style file to use when formatting email + template = ... # template to use when formatting email + incoming = ... # template to use when run as incoming hook + changegroup = ... # template when run as changegroup hook + maxdiff = 300 # max lines of diffs to include (0=none, -1=all) + maxsubject = 67 # truncate subject line longer than this + diffstat = True # add a diffstat before the diff content + sources = serve # notify if source of incoming changes in this list + # (serve == ssh or http, push, pull, bundle) + [email] + from = user@host.com # email address to send as if none given + [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. + + [usersubs] + # key is subscriber email, value is ","-separated list of glob patterns + user@host = pattern + + [reposubs] + # key is glob pattern, value is ","-separated list of subscriber emails + pattern = user@host + + glob patterns are matched against path to repo root. + + if you like, you can put notify config file in repo that users can + push changes to, they can manage their own subscriptions.''' from mercurial.i18n import _ from mercurial.node import bin, short
--- a/hgext/rebase.py Thu Jun 12 11:49:13 2008 +0200 +++ b/hgext/rebase.py Sat Oct 18 16:56:39 2008 +0200 @@ -5,7 +5,7 @@ # This software may be used and distributed according to the terms # of the GNU General Public License, incorporated herein by reference. -''' Rebasing feature +'''move sets of revisions to a different ancestor This extension lets you rebase changesets in an existing Mercurial repository.
--- a/tests/test-keyword.out Thu Jun 12 11:49:13 2008 +0200 +++ b/tests/test-keyword.out Sat Oct 18 16:56:39 2008 +0200 @@ -55,7 +55,7 @@ keyword keyword expansion in local repositories mq patch management and development - notify (no help text available) + notify hook extension to email notifications on commits/pushes use "hg -v help keyword" to show aliases and global options % hg kwdemo