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

[PATCH] t2017: redo physical reflog existance check

From
Erick Mattos <erick.mattos@gmail.com>
Date
Jul 22, 2010, 01:46 UTC
Message-ID
<1279763190-32757-1-git-send-email-erick.mattos@gmail.com>

Commit 6e6842e wiped out physical reflog checks of tests because of redundancy and to hide low level detail of the implementation.

Although this is not a problem to all the other changes, it is laming to the tenth test. The implementation of the correspondent problem creates a "touch" reflog that must be wiped out if not used by committing the new branch.

Signed-off-by: Erick Mattos <erick.mattos@gmail.com>
---
 t/t2017-checkout-orphan.sh |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/t/t2017-checkout-orphan.sh b/t/t2017-checkout-orphan.sh
index 2d2f63f..0d5d0a0 100755
--- a/t/t2017-checkout-orphan.sh
+++ b/t/t2017-checkout-orphan.sh
@@ -93,8 +93,10 @@ test_expect_success '--orphan with -l makes reflog when core.logAllRefUpdates =
 test_expect_success 'giving up --orphan not committed when -l and core.logAllRefUpdates = false deletes reflog' '
 	git checkout master &&
 	git checkout -l --orphan eta &&
+	test -f .git/logs/refs/heads/eta &&
 	test_must_fail git rev-parse --verify eta@{0} &&
 	git checkout master &&
+	! test -f .git/logs/refs/heads/eta &&
 	test_must_fail git rev-parse --verify eta@{0}
 '
 
-- 
1.7.2.1.ga86e3
Next: Junio C Hamano
Message 1 of 8 in “t2017: redo physical reflog existance check”
  1. t2017: redo physical reflog existance checkErick Mattos, Jul 22, 2010
  2. Junio C HamanoJul 22, 2010
  3. Erick MattosJul 22, 2010
  4. Junio C HamanoJul 23, 2010
  5. Erick MattosJul 23, 2010
  6. Jonathan NiederAug 24, 2010
  7. Junio C HamanoAug 24, 2010
  8. Erick MattosAug 24, 2010

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.