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

Re: [GSoC][RFC PATCH] git-merge.adoc: detail submodule merge

From
Lucas Oshiro <lucasseikioshiro@gmail.com>
Date
Feb 19, 2025, 14:54 UTC
Message-ID
<522E8293-5248-497C-B4EB-D9C6C8251D04@gmail.com>
In-Reply-To
<CABPp-BHvutRL80QiTYx6gJbYiATOD32DrvXgQQtEy=u5oUZ9Zg@mail.gmail.com>
Show 5 quoted lines
> """
> In the case where the path is a submodule, if the submodule commit used on
> one side of the merge is a descendant of the submodule commit used on the
> other side of the merge, Git...
> """
Looks good to me!
> Yes, until `recursive` is deleted anyway.  (At which point we'll just
> remap `recursive` to mean `ort` and not have to have separate
> documentation for the two.)
Ok. I'll write for both `ort` and `recursive`.
Show 5 quoted lines
> Yeah, but we don't have a way to resolve differences for those kinds
> of changes when neither side matches the base version (unless
> something like -Xours or -Xtheirs is passed, but even then that
> belongs under the -X documentation); submodules are somewhat special
> in that regard.
Thanks again! I'll send a v2 soon.
Previous: Elijah Newren
Message 5 of 5 in “git-merge.adoc: detail submodule merge”
  1. Lucas Seiki OshiroFeb 17, 2025
  2. Elijah NewrenFeb 18, 2025
  3. Lucas OshiroFeb 18, 2025
  4. Elijah NewrenFeb 18, 2025
  5. Lucas OshiroFeb 19, 2025

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.