git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] Corrected return values in prep_for_email;

From
Alan Raison <alan@theraisons.me.uk>
Date
Dec 9, 2010, 16:00 UTC
Message-ID
<004301cb97ba$90772630$b1657290$@me.uk>
In-Reply-To
<4CFE8E97.4020508@digium.com>

Function was returning 0 for failure and 1 for success which was breaking the logic in the main loop.

Corrected to return 0 for success, 1 for failure. Function now also returns in all cases, rather than exiting.

Acked-By: Kevin P. Fleming <kpfleming@digium.com>
Signed-Off-By: Alan Raison <alan@theraisons.me.uk>
---
 contrib/hooks/post-receive-email |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/contrib/hooks/post-receive-email
b/contrib/hooks/post-receive-email
index 85724bf..f99ea95 100755
--- a/contrib/hooks/post-receive-email
+++ b/contrib/hooks/post-receive-email
@@ -144,13 +144,13 @@ prep_for_email()
 			short_refname=${refname##refs/remotes/}
 			echo >&2 "*** Push-update of tracking branch,
$refname"
 			echo >&2 "***  - no email generated."
-			exit 0
+			return 1
 			;;
 		*)
 			# 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
 			;;
 	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
 	fi
 
-	return 1
+	return 0
 }
 
 #
-- 
1.7.3.1.msysgit.0
Previous: Kevin P. FlemingNext: Junio C Hamano
Message 8 of 9 in “Corrected return values in post-receive-email.prep_for_email”
  1. Corrected return values in post-receive-email.prep_for_emailAlan Raison, Dec 7, 2010
  2. Thiago FarinaDec 7, 2010
  3. Alan RaisonDec 7, 2010
  4. Junio C HamanoDec 7, 2010
  5. Kevin P. FlemingDec 7, 2010
  6. Corrected return values in prep_for_email;Alan Raison, Dec 9, 2010
  7. Kevin P. FlemingDec 9, 2010
  8. Corrected return values in prep_for_email;Alan Raison, Dec 9, 2010
  9. Junio C HamanoDec 9, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.