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

Re: [PATCH] merge: --ff-one-only to apply FF if commit is one

From
Ruslan Yakauleu <ruslan.yakauleu@gmail.com>
Date
Nov 1, 2023, 06:34 UTC
Message-ID
<aa3559d6-0e05-4c7a-818e-8a0cb05e908b@gmail.com>
In-Reply-To
<xmqqa5ryxn8i.fsf@gitster.g>
 > And the only effect to have the "--ff-one-only" option is to allow
 > you *not* to look at what is on the side branch.

Moreover, it allows not to forget choose the right way and allow use a lot of external tools (GitExtensions for example) as not all in command are console ninja

Currently, when complex features merged with --ff accidentally we have to do in main branch something like $ git reset ... $ git checkout <some_old_commit_which_we_have_to_find> $ git merge --no-ff <latest commit> $ git push --force

And that's what I prefer to avoid

-- Ruslan

Previous: Junio C HamanoNext: Kristoffer Haugsbakk
Message 11 of 15 in “merge: --ff-one-only to apply FF if commit is one”
  1. merge: --ff-one-only to apply FF if commit is oneRuslan Yakauleu via GitGitGadget, Oct 25, 2023
  2. Kristoffer HaugsbakkOct 25, 2023
  3. Ruslan YakauleuOct 25, 2023
  4. Kristoffer HaugsbakkOct 25, 2023
  5. Taylor BlauOct 30, 2023
  6. Junio C HamanoOct 31, 2023
  7. Ruslan YakauleuOct 31, 2023
  8. Junio C HamanoOct 31, 2023
  9. Kristoffer HaugsbakkOct 31, 2023
  10. Junio C HamanoNov 1, 2023
  11. Ruslan YakauleuNov 1, 2023
  12. Kristoffer HaugsbakkNov 1, 2023
  13. Junio C HamanoNov 1, 2023
  14. Ruslan YakauleuOct 31, 2023
  15. Ruslan YakauleuOct 26, 2023

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.