From 7497e3829075ed202b1cae02d57b2f5a67536d34 Mon Sep 17 00:00:00 2001 From: "Kyle J. McKay" Date: Mon, 29 Jun 2020 16:38:50 -0700 Subject: [PATCH] jobd/gc.sh: safely unset gitweb.lastgc The `git config --unset ` command fails with a non-zero exit code if is not actually set. Ignore the return code as we don't care if it's already unset. Signed-off-by: Kyle J. McKay --- jobd/gc.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/jobd/gc.sh b/jobd/gc.sh index 25345f5..9a40675 100755 --- a/jobd/gc.sh +++ b/jobd/gc.sh @@ -775,7 +775,7 @@ if [ -n "$isminigc" ]; then # We shouldn't be in a .delaygc state at this point, but if # we are then nuke it because we really need a full gc now rm -f .delaygc - git config --unset gitweb.lastgc + git config --unset gitweb.lastgc || : rm -f "$lockf" git update-server-info # just in case progress "- [$proj] mini garbage check triggering full gc too many packs ($(date))" -- 2.11.4.GIT