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

Re: What's cooking in git.git (Jul 2013, #03; Tue, 9)

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Jul 23, 2013, 07:23 UTC
Message-ID
<CALkWK0kmcQ1ws143H7O6q9kRmdBxMDVYBWVBKp+0Hy0acpn7VA@mail.gmail.com>
In-Reply-To
<7vr4f7tjo0.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> * mv/merge-ff-tristate (2013-07-02) 1 commit
>   (merged to 'next' on 2013-07-09 at c32b95d)
>  + merge: handle --ff/--no-ff/--ff-only as a tri-state option

Sorry I didn't notice sooner, but I was confused by the second test title this added:

test_expect_success 'option --ff-only overwrites merge.ff=only config' '
	git reset --hard c0 &&
	test_config merge.ff only &&
	git merge --no-ff c1
'
How is --ff-only overwriting merge.ff=only here?  Was it a typo?
-- 8< --
diff --git a/t/t7600-merge.sh b/t/t7600-merge.sh
index 3ff5fb8..aea8137 100755
--- a/t/t7600-merge.sh
+++ b/t/t7600-merge.sh
@@ -502,7 +502,7 @@ test_expect_success 'option --ff-only overwrites --no-ff' '
 	test_must_fail git merge --no-ff --ff-only c2
 '

-test_expect_success 'option --ff-only overwrites merge.ff=only config' '
+test_expect_success 'option --no-ff overwrites merge.ff=only config' '
 	git reset --hard c0 &&
 	test_config merge.ff only &&
 	git merge --no-ff c1
Previous: Ramsay JonesNext: Miklos Vajna
Message 11 of 13 in “What's cooking in git.git (Jul 2013, #03; Tue, 9)”
  1. Junio C HamanoJul 9, 2013
  2. Jeff KingJul 10, 2013
  3. Kyle McKayJul 10, 2013
  4. Junio C HamanoJul 11, 2013
  5. Matthieu MoyJul 10, 2013
  6. Junio C HamanoJul 11, 2013
  7. Ramsay JonesJul 15, 2013
  8. Junio C HamanoJul 15, 2013
  9. Junio C HamanoJul 19, 2013
  10. Ramsay JonesJul 20, 2013
  11. Ramkumar RamachandraJul 23, 2013
  12. Miklos VajnaJul 23, 2013
  13. Junio C HamanoJul 23, 2013

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.