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

override merge.ff = false using --ff-only

From
Matt McClure <matthewlmcclure@gmail.com>
Date
May 22, 2013, 13:21 UTC
Message-ID
<CAJELnLFqzVBd57vudsCFrTNMVxETO75GT5T5NO0sDMtgHZJU6g@mail.gmail.com>
In-Reply-To
<CAJELnLEGCshD9z9get62+T6Z83OdPJ+A5BNSzsHA1_OC1Q00Hw@mail.gmail.com>

I naively tried to override merge.ff = false using --ff-only on the command line. I expected that it would override the configured default and perform a fast-forward merge. Instead, it said:

    $ git config -l | grep -F 'merge.ff'
    merge.ff=false
    $ git merge --ff-only foo
    fatal: You cannot combine --no-ff with --ff-only.
On the other hand, I see that --ff works just fine in the same initial state.
    $ git merge --ff foo
    Updating b869407..17b5495
    Fast-forward
    ...
     4 files changed, 2 insertions(+), 5 deletions(-)

Would it be better if --ff-only refused to merge only if the commits themselves prevented fast-forwarding?

-- Matt McClure http://matthewlmcclure.com http://www.mapmyfitness.com/profile/matthewlmcclure

Next: Yann Droneaud
Message 1 of 3 in “override merge.ff = false using --ff-only”
  1. Matt McClureMay 22, 2013
  2. Yann DroneaudMay 22, 2013
  3. Junio C HamanoMay 22, 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.