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

[PATCH] rebase: fix run_specific_rebase's use of "return" on FreeBSD

From
Matthieu Moy <matthieu.moy@imag.fr>
Date
Sep 9, 2013, 08:53 UTC
Message-ID
<1378716795-5420-1-git-send-email-Matthieu.Moy@imag.fr>

Since a1549e10, git-rebase--am.sh uses the shell's "return" statement, to mean "return from the current file inclusion", which is POSIXly correct, but badly interpreted on FreeBSD, which returns from the current function, hence skips the finish_rebase statement that follows the file inclusion.

Make the use of "return" portable by using the file inclusion as the last statement of a function.

Reported-by: Christoph Mallon <christoph.mallon@gmx.de>
Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>
---
I sent the patch inline in a conversation and got no feedback.
Resending as a proper patch.
 git-rebase.sh | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/git-rebase.sh b/git-rebase.sh
index 8d7659a..226752f 100755
--- a/git-rebase.sh
+++ b/git-rebase.sh
@@ -167,13 +167,22 @@ You can run "git stash pop" or "git stash drop" at any time.
 	rm -rf "$state_dir"
 }
 
-run_specific_rebase () {
+run_specific_rebase_internal () {
 	if [ "$interactive_rebase" = implied ]; then
 		GIT_EDITOR=:
 		export GIT_EDITOR
 		autosquash=
 	fi
+	# On FreeBSD, the shell's "return" returns from the current
+	# function, not from the current file inclusion.
+	# run_specific_rebase_internal has the file inclusion as a
+	# last statement, so POSIX and FreeBSD's return will do the
+	# same thing.
 	. git-rebase--$type
+}
+
+run_specific_rebase () {
+	run_specific_rebase_internal
 	ret=$?
 	if test $ret -eq 0
 	then
-- 
1.8.4.5.g8688bea
Next: Ramkumar Ramachandra
Message 1 of 3 in “rebase: fix run_specific_rebase's use of "return" on FreeBSD”
  1. rebase: fix run_specific_rebase's use of "return" on FreeBSDMatthieu Moy, Sep 9, 2013
  2. Ramkumar RamachandraSep 9, 2013
  3. Junio C HamanoSep 9, 2013

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.