1 file changed, 3 insertions, 4 deletions

diff --git a/custom/hooks/post-receive.cgit-cache b/custom/hooks/post-receive.cgit-cacheindex 235de277..4825a441 100755--- a/custom/hooks/post-receive.cgit-cache+++ b/custom/hooks/post-receive.cgit-cache@@ -4,7 +4,7 @@ # show up right away instead of once the cache-*-ttl minutes have passed. # # This only matters when cache-size in your cgitrc is above 0, which turns-# the cache on.  With it off the hook does nothing and costs one stat call.+# the cache on. # # cgit names each cache slot after a hash of the request url, so there is no # way to expire one repository's pages on their own and this clears the lot.@@ -16,9 +16,8 @@ # change the value in your cgitrc then you must also change it here. # # The web server owns the cache root, so the pushing user needs write access-# to it.  Making the directory group writable and putting both users in that-# group is usually enough.  Nothing here fails a push if that access is-# missing, since a stale page is not worth rejecting a push over.+# to it.  Nothing here exits nonzero when that access is missing, so the+# pusher is not shown an error over a stale page. # # To install the hook, copy (or link) it to the file "hooks/post-receive" in # each of your repositories.  Git runs one post-receive per repository, so
diff --git a/custom/hooks/post-receive.cgit-cache b/custom/hooks/post-receive.cgit-cache
index 235de277..4825a441 100755
--- a/custom/hooks/post-receive.cgit-cache
+++ b/custom/hooks/post-receive.cgit-cache
@@ -4,7 +4,7 @@
 # show up right away instead of once the cache-*-ttl minutes have passed.
 #
 # This only matters when cache-size in your cgitrc is above 0, which turns
-# the cache on.  With it off the hook does nothing and costs one stat call.
+# the cache on.
 #
 # cgit names each cache slot after a hash of the request url, so there is no
 # way to expire one repository's pages on their own and this clears the lot.
@@ -16,9 +16,8 @@
 # change the value in your cgitrc then you must also change it here.
 #
 # The web server owns the cache root, so the pushing user needs write access
-# to it.  Making the directory group writable and putting both users in that
-# group is usually enough.  Nothing here fails a push if that access is
-# missing, since a stale page is not worth rejecting a push over.
+# to it.  Nothing here exits nonzero when that access is missing, so the
+# pusher is not shown an error over a stale page.
 #
 # To install the hook, copy (or link) it to the file "hooks/post-receive" in
 # each of your repositories.  Git runs one post-receive per repository, so