From: Christian Couder <chriscool@tuxfamily.org>
To: Junio Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Johannes Sixt <j.sixt@viscovery.net>
Subject: [PATCH v2] Bisect reset: remove bisect refs that may have been packed.
Date: Thu, 15 Nov 2007 08:18:07 +0100 [thread overview]
Message-ID: <20071115081807.06fe092b.chriscool@tuxfamily.org> (raw)
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 reply other threads:[~2007-11-15 7:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 7:18 Christian Couder [this message]
2007-11-15 8:18 ` [PATCH v2] Bisect reset: remove bisect refs that may have been packed Junio C Hamano
2007-11-15 8:27 ` Johannes Sixt
2007-11-15 8:49 ` Shawn O. Pearce
2007-11-15 8:52 ` Jeff King
2007-11-15 12:10 ` Johannes Schindelin
2007-11-15 8:34 ` Junio C Hamano
2007-11-15 9:00 ` [PATCH 1/3] git-bisect: war on "sed" Junio C Hamano
2007-11-15 9:29 ` Miles Bader
2007-11-15 9:36 ` Wincent Colaiuta
2007-11-15 9:53 ` Miles Bader
2007-11-15 10:06 ` Andreas Ericsson
2007-11-15 10:14 ` David Kastrup
[not found] ` <86tznn4y7v.fsf@lola.quinscape.zz>
2007-11-15 11:00 ` Miles Bader
2007-11-15 11:18 ` David Kastrup
2007-11-15 12:59 ` Miles Bader
2007-11-15 9:01 ` [PATCH 2/3] git-bisect: use update-ref to mark good/bad commits Junio C Hamano
2007-11-15 9:01 ` [PATCH 3/3] git-bisect: modernize branch shuffling hack Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071115081807.06fe092b.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).