From: Lars Noschinski <lars@public.noschinski.de>
To: git@vger.kernel.org
Cc: gitster@pobox.com, Lars Noschinski <lars@public.noschinski.de>
Subject: [PATCH] post-receive-email: do not call sendmail if no mail was generated
Date: Fri, 28 Aug 2009 19:39:47 +0200 [thread overview]
Message-ID: <1251481187-6361-1-git-send-email-lars@public.noschinski.de> (raw)
contrib/hooks/post-receive-email used to call the send_mail function
(and thus, /usr/sbin/sendmail), even if generate_mail returned an error.
This is problematic, as the sendmail binary provided by exim4 generates
an error mail if provided with an empty input.
Therefore, this commit changes post-receive-email to only call sendmail
if generate_mail returned without error.
Signed-off-by: Lars Noschinski <lars@public.noschinski.de>
---
contrib/hooks/post-receive-email | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
Obvious drawback of this solution is that the mails are kept in memory as a
whole. But the mails should be small enough, so that this does not hurt.
I'm not sure how to write a test for this bug, as the hook (correctly) uses an
absolute path to call sendmail.
diff --git a/contrib/hooks/post-receive-email b/contrib/hooks/post-receive-email
index 2a66063..818a270 100755
--- a/contrib/hooks/post-receive-email
+++ b/contrib/hooks/post-receive-email
@@ -684,6 +684,9 @@ if [ -n "$1" -a -n "$2" -a -n "$3" ]; then
else
while read oldrev newrev refname
do
- generate_email $oldrev $newrev $refname | send_mail
+ mail="$(generate_email $oldrev $newrev $refname)"
+ if [ $? -eq 0 ]; then
+ printf '%s' "$mail" | send_mail
+ fi
done
fi
--
1.6.3.3
next reply other threads:[~2009-08-28 18:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 17:39 Lars Noschinski [this message]
2009-09-08 9:20 ` [PATCH] post-receive-email: do not call sendmail if no mail was generated Lars Noschinski
2009-09-08 16:57 ` Junio C Hamano
2009-09-08 18:55 ` Lars Noschinski
2009-09-08 19:00 ` Lars Noschinski
2009-09-08 20:15 ` Junio C Hamano
2009-09-08 20:59 ` Lars Noschinski
2009-09-08 21:49 ` Junio C Hamano
2009-09-08 21:12 ` Andy Parkins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1251481187-6361-1-git-send-email-lars@public.noschinski.de \
--to=lars@public.noschinski.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).