summaryrefslogtreecommitdiff
path: root/doc/todo/mercurial
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2007-12-07 21:15:43 -0500
committerJoey Hess <joey@kitenet.net>2007-12-07 21:15:43 -0500
commitb2906e06687e92ea4302fda8d3b0e941a605d5c0 (patch)
tree14a347e1a00a101231ff6b46f989fd177ed63ccf /doc/todo/mercurial
parent4f5916db5c95c2856a6d621d48116b85c2b7552e (diff)
response
Diffstat (limited to 'doc/todo/mercurial')
-rw-r--r--doc/todo/mercurial/discussion.mdwn9
1 files changed, 8 insertions, 1 deletions
diff --git a/doc/todo/mercurial/discussion.mdwn b/doc/todo/mercurial/discussion.mdwn
index c2d175565..de3670d9b 100644
--- a/doc/todo/mercurial/discussion.mdwn
+++ b/doc/todo/mercurial/discussion.mdwn
@@ -1,2 +1,9 @@
How does the lack of a post-commit hook for mercurial affect my ikiwiki installation?
-I want to use ikiwiki with one of the distributed scm systems and mercurial appears have the best balance of mature ikiwiki support and windows support. \ No newline at end of file
+I want to use ikiwiki with one of the distributed scm systems and mercurial appears have the best balance of mature ikiwiki support and windows support.
+
+> Without a post-commit hook, changes committed to the wiki (either via
+> mercurial or via the web) will not automatically cause ikiwiki to run to
+> rebuild the changed pages. The parent page has an example of how to
+> configure mercurial to run ikiwiki as a post-commit hook. Someone just
+> needs to test this (including my suggested change) and then we could
+> document it in the setup page. --[[Joey]]