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

Re: Question about merge & cherry pick

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Nov 7, 2024, 12:02 UTC
Message-ID
<ZyysPeBRXvTAxLVf@tapette.crustytoothpaste.net>
In-Reply-To
<a129e967-efba-48ba-b5a0-1abbb0af5c9d@maurel.me>
On 2024-11-07 at 10:32:06, Julien Maurel wrote:
> Ok, I didn't have this vision about how merge is apply, thanks.
> There is no option to merge by considering each commit individually ?
> Rebase do it but not applicable in my case :)

There's no way to do a merge commit-by commit. The recommendation is to do a rebase, since it essentially does a commit-by-commit merge under the hood (due to using the merge machinery). The title of the FAQ entry at [0] doesn't perfectly describe your case, but it does sort of explain it and it explains how the merge and rebase machinery works.

[0] https://git-scm.com/docs/gitfaq#merge-two-revert-one
-- 
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA
Previous: Julien MaurelNext: Johannes Sixt
Message 4 of 5 in “Question about merge & cherry pick”
  1. Julien MaurelNov 6, 2024
  2. Johannes SixtNov 7, 2024
  3. Julien MaurelNov 7, 2024
  4. brian m. carlsonNov 7, 2024
  5. Johannes SixtNov 7, 2024

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.