From d33a651051ef03e1d61fde71113c873972d258b4 Mon Sep 17 00:00:00 2001
From: "http://christian.amsuess.com/chrysn"
 <http://christian.amsuess.com/chrysn@web>
Date: Thu, 30 Jan 2014 11:24:34 -0400
Subject: [PATCH] on ikiwiki with gitolite

---
 ...wiki_and_master_git_repository_on_different_machines.mdwn | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/doc/tips/Hosting_Ikiwiki_and_master_git_repository_on_different_machines.mdwn b/doc/tips/Hosting_Ikiwiki_and_master_git_repository_on_different_machines.mdwn
index baf7ac6c8..35feacb71 100644
--- a/doc/tips/Hosting_Ikiwiki_and_master_git_repository_on_different_machines.mdwn
+++ b/doc/tips/Hosting_Ikiwiki_and_master_git_repository_on_different_machines.mdwn
@@ -149,3 +149,8 @@ the IkiWiki machine, and here is the deadlock. Explanations of the command:
 - *Using [[gitolite|https://github.com/sitaramc/gitolite]] to manage
   repositories on the git machine* Simply replace the manipulations of git on
   the git machine by the corresponding manipulations using gitolite.
+    * With gitolite, you can use this line in a `post-update` hook:
+
+        `[ x"$GL_USER" = x"`*`gitolite-user`*`" ] || wget ...`
+
+        thus, you filter out precisely the events that originate from the server-to-be-pinged, no matter what the commit id says. (For example, if you push commits you created on a local CGI ikiwiki, they'd be called '@web' as well).