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

[PATCH] git-am: initialize variable $resume on startup

From
Gerrit Pape <pape@smarden.org>
Date
Aug 6, 2007, 14:15 UTC
Message-ID
<20070806141530.10422.qmail@8bd9c2a0b9ecab.315fe32.mid.smarden.org>
In-Reply-To
<20070803201405.GB12430@artemis.corp>

git-am expects the variable $resume to be empty or unset, which might not be the case if $resume is set in the user's environment. So initialize it to an empty value on startup.

The problem was noticed by Pierre Habouzit and reported through
 http://bugs.debian.org/435807
Signed-off-by: Gerrit Pape <pape@smarden.org>
---
 git-am.sh |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/git-am.sh b/git-am.sh
index 6cf0eee..b5ed8ca 100755
--- a/git-am.sh
+++ b/git-am.sh
@@ -103,7 +103,8 @@ It does not apply to blobs recorded in its index."
 }
 
 prec=4
-dotest=.dotest sign= utf8=t keep= skip= interactive= resolved= binary= resolvemsg=
+dotest=.dotest sign= utf8=t keep= skip= interactive= resolved= binary=
+resolvemsg= resume=
 git_apply_opt=
 
 while case "$#" in 0) break;; esac
-- 
1.5.3.GIT
Previous: Pierre HabouzitNext: Junio C Hamano
Message 2 of 3 in “git shell scripts flaw wrt dirty env”
  1. Pierre HabouzitAug 3, 2007
  2. git-am: initialize variable $resume on startupGerrit Pape, Aug 6, 2007
  3. Junio C HamanoAug 6, 2007

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.