X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/1a1c0c03b1768b02d4a40a88d5931954218c5748..2121cac131765e0d7524e27e821b0bc4ceb36d40:/doc/rcs/details.mdwn

diff --git a/doc/rcs/details.mdwn b/doc/rcs/details.mdwn
index 0a9feada5..089221cab 100644
--- a/doc/rcs/details.mdwn
+++ b/doc/rcs/details.mdwn
@@ -1,6 +1,6 @@
 A few bits about the RCS backends
 
-[[toc ]]
+[[!toc ]]
 
 ## Terminology
 
@@ -121,7 +121,7 @@ towards transmitting changes with standalone patch bundles (often by email) as d
 >>> exactly one darcs repo. I think we can simplify and say conflicting web
 >>> edits are not allowed, like most current wiki engines. I don't see that 
 >>> saving (so much) context in the html is necessary, then. 
->>> bma, I would like to see your code. --[[Simon Michael]]
+>>> bma, I would like to see your code. --[[Simon_Michael]]
 >>> PS ah, there it is. Let's continue on the [[todo/darcs]] page.
 
 
@@ -266,8 +266,7 @@ on the same local machine, I suggest to create the latter with the "`git clone -
 command to save disk space.
 
 Note that, as a rule of thumb, you should always put the rcs wrapper (`post-update`)
-into the master repository (`.git/hooks/`) as can be noticed in the Git wrappers of
-the sample [[ikiwiki.setup]].
+into the master repository (`.git/hooks/`).
 
 Here is how a web edit works with ikiwiki and git:
 
@@ -281,6 +280,9 @@ Here is a how a commit from a remote repository works:
 
 * git-commit in the remote repository
 * git-push, pushes the commit to the master repo on the server
+* (Optionally, the master repo's pre-receive hook runs, and checks that the
+  update only modifies files that the pushing user is allowed to update. 
+  If not, it aborts the receive.)
 * the master repo's post-update hook notices this update, and runs ikiwiki
 * ikiwiki notices the modifies page source, and compiles it