From: "Kevin P. Fleming" <kpfleming@digium.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Alan Raison <alan@theraisons.me.uk>, git@vger.kernel.org
Subject: Re: [PATCH] Corrected return values in post-receive-email.prep_for_email
Date: Tue, 07 Dec 2010 13:44:23 -0600 [thread overview]
Message-ID: <4CFE8E97.4020508@digium.com> (raw)
In-Reply-To: <7v1v5tqswl.fsf@alter.siamese.dyndns.org>
On 12/07/2010 01:34 PM, Junio C Hamano wrote:
> "Alan Raison"<alan@theraisons.me.uk> writes:
>
>> ---
>> contrib/hooks/post-receive-email | 6 +++---
>> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> No sign-off, no description.
>
> This is a regression introduced by 53cad69 (post-receive-email: ensure
> sent messages are not empty, 2010-09-10), I think.
>
>> diff --git a/contrib/hooks/post-receive-email
>> b/contrib/hooks/post-receive-email
>> index 85724bf..020536d 100755
>> --- a/contrib/hooks/post-receive-email
>> +++ b/contrib/hooks/post-receive-email
>> @@ -150,7 +150,7 @@ prep_for_email()
>> # Anything else (is there anything else?)
>> echo>&2 "*** Unknown type of update to $refname
>> ($rev_type)"
>> echo>&2 "*** - no email generated"
>> - return 0
>> + return 1
>
> This used to "exit 1" before 53cad69 and I agree with the patch that
> signalling error with "return 1" is the right thing to do here.
>
>> ;;
>> esac
>>
>> @@ -166,10 +166,10 @@ prep_for_email()
>> esac
>> echo>&2 "*** $config_name is not set so no email will be
>> sent"
>> echo>&2 "*** for $refname update $oldrev->$newrev"
>> - return 0
>> + return 1
>
> This used to "exit 0" before 53cad69 to cause the program stop before
> sending mails. Again, I agree with the patch that signalling error is the
> right thing to do here.
>
>> fi
>>
>> - return 1
>> + return 0
>
> And this obviously is correct.
>
> Kevin, care to review and Ack? Alan, care to add a few lines of patch
> description and sign-off?
Acked-by: Kevin P. Fleming <kpfleming@digium.com>
Yeah, this is clearly my breakage; our internal version of this script
is so different that it has become hard to backport fixes to the
upstream version... or I just did a terrible job of it.
Alan, while you are in there fixing this, there is a remaining 'exit 0'
in prep_for_email (at line 147) that should be 'return 1' instead.
--
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
skype: kpfleming | jabber: kfleming@digium.com
Check us out at www.digium.com & www.asterisk.org
next prev parent reply other threads:[~2010-12-07 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 16:32 [PATCH] Corrected return values in post-receive-email.prep_for_email Alan Raison
2010-12-07 16:50 ` Thiago Farina
2010-12-07 17:10 ` Alan Raison
2010-12-07 19:34 ` Junio C Hamano
2010-12-07 19:44 ` Kevin P. Fleming [this message]
2010-12-09 13:24 ` [PATCH] Corrected return values in prep_for_email; Alan Raison
2010-12-09 15:19 ` Kevin P. Fleming
2010-12-09 16:03 ` Alan Raison
2010-12-09 17:38 ` Junio C Hamano
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=4CFE8E97.4020508@digium.com \
--to=kpfleming@digium.com \
--cc=alan@theraisons.me.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.