Bug#428413: commit mail sender messes up order of arguments

From

Jonathan Nieder <jrnieder@gmail.com>

Date

May 16, 2010, 01:26 UTC

Message-ID

<20100516012615.GA5599@progeny.tock>

In-Reply-To

<20070611150405.GA4211@lapse.madduck.net>

martin f krafft wrote:

> According to the default hooks/post-receive file, the hook is called
> with three arguments on stdin:
> 
>   <oldrev> <newrev> <refname>
> 
> This leads people to assume that in command-line mode, the order
> should be the same. But it's not, because the email hook instead
> calls:
> 
>   generate_email $2 $3 $1
> 
> this is at least misleading and not documented anywhere.

So maybe we should document it.

Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
---
 contrib/hooks/post-receive-email |    7 +++++++
 1 files changed, 7 insertions(+), 0 deletions(-)

diff --git a/contrib/hooks/post-receive-email b/contrib/hooks/post-receive-email
index 58a35c8..30ae63d 100755
--- a/contrib/hooks/post-receive-email
+++ b/contrib/hooks/post-receive-email
@@ -23,6 +23,13 @@
 # possible for the email to be from someone other than the person doing the
 # push.
 #
+# To help with debugging and use on pre-v1.5.1 git servers, this script will
+# also obey the interface of hooks/update, taking its arguments on the
+# command line.  Unfortunately, hooks/update is called once for each ref.
+# To avoid firing one email per ref, this script just prints its output to
+# the screen when used in this mode.  The output can then be redirected if
+# wanted.
+#
 # Config
 # ------
 # hooks.mailinglist

-- 
1.7.1




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org