web commit by http://edward.myopenid.com/: fix broken link to http://git.or.cz/gitwik...

[git.ikiwiki.info.git] / doc / rcs / git.mdwn

diff --git a/doc/rcs/git.mdwn b/doc/rcs/git.mdwn
index 0353d153558efd93c7f9403782996be7e8f028da..f97131742518770d30bdaa63bba1af9554d02d36 100644 (file)
--- a/doc/rcs/git.mdwn
+++ b/doc/rcs/git.mdwn
@@ -22,7 +22,7 @@ but it works the best for typical ikiwiki use.
 and git.
 
 It is **paramount** that you **never** push to the non-bare repository
-([this FAQ entry explains why](http://git.or.cz/gitwiki/GitFaq#head-b6a3d85f677763313159eb39f7dbf4579d4ee28b)).
+([this FAQ entry explains why](http://git.or.cz/gitwiki/GitFaq#head-b96f48bc9c925074be9f95c0fce69bcece5f6e73)).
 Instead, if you want to work on the wiki from a remote machine, clone
 the bare repository, using either the `git` transport (if available), or
 `ssh`.
@@ -39,7 +39,7 @@ should go to the bare repository, which has a `post-update` hook that uses
 ikiwiki to pull the changes to the srcdir.
 
 One setup that will work is to put all committers in a group (say,
-ikiwiki), and use permissions to allow that group to commit to the bare git
+"ikiwiki"), and use permissions to allow that group to commit to the bare git
 repository. Make both the post-update hook and ikiwiki.cgi be setgid
 to the group, as well as suid to the user who admins the wiki. The
 `wrappergroup` [[setup_file_option|usage]] can be used to make the wrappers