From: Marc Branchaud <marcnarc@xiplink.com>
To: "Kevin P. Fleming" <kpfleming@digium.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Optional limit for number of lines generated by script
Date: Wed, 14 Jul 2010 12:41:49 -0400 [thread overview]
Message-ID: <4C3DE8CD.5060103@xiplink.com> (raw)
In-Reply-To: <1279055909-4340-1-git-send-email-kpfleming@digium.com>
Thanks for addressing my comments!
M.
On 10-07-13 05:18 PM, Kevin P. Fleming wrote:
> We have become used to the features of svnmailer when used with Subversion,
> and one of those useful features is that it can limit the maximum length
> (in lines) of a commit email message. This is terribly useful since once the
> goes beyond a reasonable number of lines, nobody is going to read the remainder,
> and if they really want the entire contents of the commits, they can use
> git itself to get them using the revision IDs present in the message already.
>
> Change the post-receive-email script to respond to an 'emailmaxlines' config key
> which, if specified, will limit the number of lines generated (including
> headers); any lines beyond the limit are suppressed, and a final line is added
> indicating the number that were suppressed.
> ---
> contrib/hooks/post-receive-email | 33 ++++++++++++++++++++++++++++++++-
> 1 files changed, 32 insertions(+), 1 deletions(-)
>
> diff --git a/contrib/hooks/post-receive-email b/contrib/hooks/post-receive-email
> index 30ae63d..d3b5fab 100755
> --- a/contrib/hooks/post-receive-email
> +++ b/contrib/hooks/post-receive-email
> @@ -55,6 +55,11 @@
> # "t=%s; printf 'http://.../?id=%%s' \$t; echo;echo; git show -C \$t; echo"
> # Be careful if "..." contains things that will be expanded by shell "eval"
> # or printf.
> +# hooks.emailmaxlines
> +# The maximum number of lines that should be included in the generated
> +# email (including its headers). If not specified, there is no limit.
> +# Lines beyond the limit are suppressed and counted, and a final
> +# line is added indicating the number of suppressed lines.
> #
> # Notes
> # -----
> @@ -642,6 +647,27 @@ show_new_revisions()
> }
>
>
> +limit_lines()
> +{
> + lines=0
> + skipped=0
> + while IFS="" read line
> + do
> + lines=$((lines + 1))
> + if [ $lines -gt $1 ]
> + then
> + skipped=$((skipped + 1))
> + else
> + echo "$line"
> + fi
> + done
> + if [ $skipped -ne 0 ]
> + then
> + echo "... $skipped lines suppressed ..."
> + fi
> +}
> +
> +
> send_mail()
> {
> if [ -n "$envelopesender" ]; then
> @@ -679,6 +705,7 @@ announcerecipients=$(git config hooks.announcelist)
> envelopesender=$(git config hooks.envelopesender)
> emailprefix=$(git config hooks.emailprefix || echo '[SCM] ')
> custom_showrev=$(git config hooks.showrev)
> +maxlines=$(git config hooks.emailmaxlines)
>
> # --- Main loop
> # Allow dual mode: run from the command line just like the update hook, or
> @@ -691,6 +718,10 @@ if [ -n "$1" -a -n "$2" -a -n "$3" ]; then
> else
> while read oldrev newrev refname
> do
> - generate_email $oldrev $newrev $refname | send_mail
> + if [ -z "$maxlines" ]; then
> + generate_email $oldrev $newrev $refname | send_mail
> + else
> + generate_email $oldrev $newrev $refname | limit_lines $maxlines | send_mail
> + fi
> done
> fi
prev parent reply other threads:[~2010-07-14 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 19:03 [PATCH] Add support for limiting number of lines generated in messages by post-receive-email Kevin P. Fleming
2010-07-12 16:47 ` Marc Branchaud
2010-07-13 20:56 ` Kevin P. Fleming
2010-07-12 17:10 ` Ævar Arnfjörð Bjarmason
2010-07-13 21:18 ` [PATCH] Optional limit for number of lines generated by script Kevin P. Fleming
2010-07-13 21:43 ` Andreas Schwab
2010-07-15 14:51 ` [PATCH] post-receive-email: optional message line count limit Kevin P. Fleming
2010-07-15 17:36 ` Junio C Hamano
2010-07-16 19:13 ` Kevin P. Fleming
2010-07-16 19:16 ` Kevin P. Fleming
2010-07-14 16:41 ` Marc Branchaud [this message]
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=4C3DE8CD.5060103@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=git@vger.kernel.org \
--cc=kpfleming@digium.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).