From: Stefan Beller <sbeller@google.com>
To: mhagger@alum.mit.edu, gitster@pobox.com, git@vger.kernel.org
Cc: Ronnie Sahlberg <sahlberg@google.com>,
Stefan Beller <sbeller@google.com>
Subject: [PATCH] t1402: check to delete broken refs
Date: Tue, 25 Nov 2014 14:56:06 -0800 [thread overview]
Message-ID: <1416956166-20341-1-git-send-email-sbeller@google.com> (raw)
From: Ronnie Sahlberg <sahlberg@google.com>
Signed-off-by: Ronnie Sahlberg <sahlberg@google.com>
Signed-off-by: Stefan Beller <sbeller@google.com>
---
This was also part of the ongoing series from Ronnie.
But I think the patch in this form is rather independant,
documenting the current state of "git branch -d", so it's
fine to have it in now.
t/t1402-check-ref-format.sh | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/t/t1402-check-ref-format.sh b/t/t1402-check-ref-format.sh
index e5dc62e..08af156 100755
--- a/t/t1402-check-ref-format.sh
+++ b/t/t1402-check-ref-format.sh
@@ -197,4 +197,12 @@ invalid_ref_normalized 'heads///foo.lock'
invalid_ref_normalized 'foo.lock/bar'
invalid_ref_normalized 'foo.lock///bar'
+test_expect_failure 'git branch -d can delete ref with broken sha1' '
+ echo "pointing nowhere" > .git/refs/heads/brokensha1 &&
+ test_when_finished "rm -f .git/refs/heads/brokensha1" &&
+ git branch -d brokensha1 &&
+ git branch >output &&
+ ! grep -e "brokensha1" output
+'
+
test_done
--
2.2.0.rc3
next reply other threads:[~2014-11-25 22:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 22:56 Stefan Beller [this message]
2014-11-26 0:35 ` [PATCH] t1402: check to delete broken refs Jonathan Nieder
2014-11-26 0:42 ` Stefan Beller
2014-11-26 0:59 ` [PATCHv2] branch -d: test if we can " Stefan Beller
2014-11-26 8:49 ` Michael Haggerty
2014-11-26 18:43 ` Junio C Hamano
2014-11-26 5:05 ` [PATCH] t1402: check to " Torsten Bögershausen
2014-11-26 18:37 ` [PATCHv3] branch -d: test if we can " Stefan Beller
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=1416956166-20341-1-git-send-email-sbeller@google.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mhagger@alum.mit.edu \
--cc=sahlberg@google.com \
/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).