From 52b16186c407188f27d01e86cd5c985168d976b6 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 28 Jan 2008 17:33:22 -0500 Subject: [PATCH] update comment This is not only called from post-update in all configurations. Also, the comment was innaccurate about what the post-update hook is passed. --- IkiWiki/Rcs/git.pm | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/IkiWiki/Rcs/git.pm b/IkiWiki/Rcs/git.pm index fea1c11eb..b538c524f 100644 --- a/IkiWiki/Rcs/git.pm +++ b/IkiWiki/Rcs/git.pm @@ -424,14 +424,15 @@ sub rcs_recentchanges ($) { #{{{ sub rcs_notify () { #{{{ # Send notification mail to subscribed users. # + # This is typically run as the post-update hook, though some setups + # may run it from the post-commit hook too. + # # In usual Git usage, hooks/update script is presumed to send # notification mails (see git-receive-pack(1)). But we prefer # hooks/post-update to support IkiWiki commits coming from a # cloned repository (through command line) because post-update # is called _after_ each ref in repository is updated (update - # hook is called _before_ the repository is updated). Since - # post-update hook does not accept command line arguments, we - # don't have an $ENV variable in this function. + # hook is called _before_ the repository is updated). # # Here, we rely on a simple fact: we can extract all parts of the # notification content by parsing the "HEAD" commit (which also -- 2.45.0