From: Mike Crowe <mac@mcrowe.com>
To: git@vger.kernel.org
Cc: mac@mcrowe.com
Subject: [PATCH] post-receive-email: Fix handling of hooks.emailmaxlines configuration option
Date: Thu, 11 Aug 2011 18:13:31 +0100 [thread overview]
Message-ID: <1313082811-1396-1-git-send-email-mac@mcrowe.com> (raw)
Make the hooks.emailmaxlines configuration option work correctly
again. It looks like this was broken by 53cad691.
Signed-off-by: Mike Crowe <mac@mcrowe.com>
---
contrib/hooks/post-receive-email | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/contrib/hooks/post-receive-email b/contrib/hooks/post-receive-email
index fa6d41a..ab6d298 100755
--- a/contrib/hooks/post-receive-email
+++ b/contrib/hooks/post-receive-email
@@ -85,7 +85,6 @@ prep_for_email()
oldrev=$(git rev-parse $1)
newrev=$(git rev-parse $2)
refname="$3"
- maxlines=$4
# --- Interpret
# 0000->1234 (create)
@@ -198,6 +197,8 @@ prep_for_email()
generate_email()
{
# Email parameters
+ maxlines=$1
+
# The email subject will contain the best description of the ref
# that we can build from the parameters
describe=$(git describe $rev 2>/dev/null)
--
1.7.2.5
reply other threads:[~2011-08-11 17:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1313082811-1396-1-git-send-email-mac@mcrowe.com \
--to=mac@mcrowe.com \
--cc=git@vger.kernel.org \
/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).