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

[PATCH v2] Bisect reset: remove bisect refs that may have been packed.

From
Christian Couder <chriscool@tuxfamily.org>
Date
Nov 15, 2007, 07:18 UTC
Message-ID
<20071115081807.06fe092b.chriscool@tuxfamily.org>

If refs were ever packed in the middle of bisection, the bisect refs were not removed from the "packed-refs" file.

This patch fixes this problem by using "git update-ref -d $ref $hash" in "bisect_clean_state".

Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
---
 git-bisect.sh               |   11 ++++++++++-
 t/t6030-bisect-porcelain.sh |   12 ++++++++++++
 2 files changed, 22 insertions(+), 1 deletions(-)
	Ooops, there was a problem with the previous patch
	if "git bisect reset" was used when not bisecting.
	Sorry.
diff --git a/git-bisect.sh b/git-bisect.sh
index 1ed44e5..584906f 100755
--- a/git-bisect.sh
+++ b/git-bisect.sh
@@ -351,7 +351,16 @@ bisect_reset() {
 
 bisect_clean_state() {
 	rm -fr "$GIT_DIR/refs/bisect"
-	rm -f "$GIT_DIR/refs/heads/bisect"
+
+	# There may be some refs packed during bisection.
+	git for-each-ref --format='%(refname) %(objectname)' \
+		"refs/bisect/*" | while read ref hash
+	do
+		git update-ref -d $ref $hash
+	done
+
+	hash=$(git show-ref --hash refs/heads/bisect)
+	test -n "$hash" && git update-ref -d refs/heads/bisect $hash
 	rm -f "$GIT_DIR/BISECT_LOG"
 	rm -f "$GIT_DIR/BISECT_NAMES"
 	rm -f "$GIT_DIR/BISECT_RUN"
diff --git a/t/t6030-bisect-porcelain.sh b/t/t6030-bisect-porcelain.sh
index 53956c0..f09db62 100755
--- a/t/t6030-bisect-porcelain.sh
+++ b/t/t6030-bisect-porcelain.sh
@@ -71,6 +71,18 @@ test_expect_success 'bisect start with one bad and good' '
 	git bisect next
 '
 
+test_expect_success 'bisect reset removes packed refs' '
+	git bisect reset &&
+	git bisect start &&
+	git bisect good $HASH1 &&
+	git bisect bad $HASH3 &&
+	git pack-refs --all --prune &&
+	git bisect next &&
+	git bisect reset &&
+	test -z "$(git for-each-ref "refs/bisect/*")" &&
+	test -z "$(git for-each-ref "refs/heads/bisect")"
+'
+
 # $HASH1 is good, $HASH4 is bad, we skip $HASH3
 # but $HASH2 is bad,
 # so we should find $HASH2 as the first bad commit
-- 
1.5.3.5.722.g789fd-dirty
Next: Junio C Hamano
Message 1 of 18 in “Bisect reset: remove bisect refs that may have been packed.”
  1. Bisect reset: remove bisect refs that may have been packed.Christian Couder, Nov 15, 2007
  2. Junio C HamanoNov 15, 2007
  3. Johannes SixtNov 15, 2007
  4. Shawn O. PearceNov 15, 2007
  5. Jeff KingNov 15, 2007
  6. Johannes SchindelinNov 15, 2007
  7. Junio C HamanoNov 15, 2007
  8. 1/3 git-bisect: war on "sed"Junio C Hamano, Nov 15, 2007
  9. Miles BaderNov 15, 2007
  10. Wincent ColaiutaNov 15, 2007
  11. Miles BaderNov 15, 2007
  12. Andreas EricssonNov 15, 2007
  13. David KastrupNov 15, 2007
  14. 2/3 git-bisect: use update-ref to mark good/bad commitsJunio C Hamano, Nov 15, 2007
  15. 3/3 git-bisect: modernize branch shuffling hackJunio C Hamano, Nov 15, 2007
  16. Miles BaderNov 15, 2007
  17. David KastrupNov 15, 2007
  18. Miles BaderNov 15, 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.