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

Re: Why "You cannot combine --squash with --no-ff" in git merge?

From
Anatoly Borodin <anatoly.borodin@gmail.com>
Date
Mar 21, 2017, 02:11 UTC
Message-ID
<oaq256$u33$1@blaine.gmane.org>
In-Reply-To
<oaq19p$kpo$1@blaine.gmane.org>
Hi All,

I made a mistake in the previous message. I'm really sorry, I need to go have some sleep right now.

Anatoly Borodin <anatoly.borodin@gmail.com> wrote:
Show 7 quoted lines
> `git merge --squash --ff` will happily move the A ref to the B commit.
> 
> But what I want, and expect, is:
> 
>         A---B'
> 
> where B' has the same tree as B.
`git merge --squash --ff` WILL create A---B'.

But it's still unclear to me why `git merge --squash --no-ff` should fail instead of doing the same as `git merge --squash --ff` does. The error message and the documentation do not give any good reasons for it.

PS In my case, I set `merge.ff=false` and run just `git merge --squash`.
-- 
Mit freundlichen Grüßen,
Anatoly Borodin
Previous: Anatoly Borodin
Message 2 of 2 in “Why "You cannot combine --squash with --no-ff" in git merge?”
  1. Anatoly BorodinMar 21, 2017
  2. Anatoly BorodinMar 21, 2017

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.