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

Re: [PATCH] refresh-index: fix bitmask assignment

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 20, 2008, 07:28 UTC
Message-ID
<7v3am5f20f.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<7vk5fhf35p.fsf@gitster.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> This hopefully protects the previous fix (and other --refresh related
> options) from future  breakages.
>
> I'll squash it in to the previous one.

Actually, I'll squash this further on top, for a reason that will become clear with the next series...

---
 t/t2103-update-index-ignore-missing.sh |    5 ++---
 1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/t/t2103-update-index-ignore-missing.sh b/t/t2103-update-index-ignore-missing.sh
index 332694e..4fbf855 100755
--- a/t/t2103-update-index-ignore-missing.sh
+++ b/t/t2103-update-index-ignore-missing.sh
@@ -62,10 +62,9 @@ test_expect_success '--unmerged --refresh' '
 	test_must_fail git update-index --refresh &&
 	git update-index --unmerged --refresh &&
 	echo 2 >two &&
+	echo "two: needs update" >expect &&
 	test_must_fail git update-index --unmerged --refresh >actual &&
-	grep two actual &&
-	! grep one actual &&
-	! grep three actual
+	test_cmp expect actual
 '
 
 test_expect_success '--ignore-submodules --refresh (1)' '
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 12 in “refresh-index: fix bitmask assignment”
  1. refresh-index: fix bitmask assignmentJunio C Hamano, Jul 20, 2008
  2. Junio C HamanoJul 20, 2008
  3. Junio C HamanoJul 20, 2008
  4. [RFC] "needs update" considered harmfulJunio C Hamano, Jul 20, 2008
  5. Jay SoffianJul 21, 2008
  6. [RFC variant 1 of 2] "needs update" considered harmfulJunio C Hamano, Jul 20, 2008
  7. [RFC variant 2 of 2] "needs update" considered harmfulJunio C Hamano, Jul 20, 2008
  8. Petr BaudisJul 20, 2008
  9. Johannes SchindelinJul 20, 2008
  10. Junio C HamanoJul 20, 2008
  11. Jay SoffianJul 21, 2008
  12. André Goddard RosaJul 20, 2008

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.