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

en/merge-tree (Was: Re: What's cooking in git.git (Feb 2022, #07; Fri, 25))

From
Elijah Newren <newren@gmail.com>
Date
Feb 26, 2022, 08:54 UTC
Message-ID
<CABPp-BG++YqesTxp+JL3XzwrogfMag1NscoMpCOExmV9z6Py9A@mail.gmail.com>
In-Reply-To
<xmqqee3q73e1.fsf@gitster.g>
On Fri, Feb 25, 2022 at 7:07 PM Junio C Hamano <gitster@pobox.com> wrote:
Show 23 quoted lines
>
> * en/merge-tree (2022-02-23) 13 commits
>  - git-merge-tree.txt: add a section on potentional usage mistakes
>  - merge-tree: add a --allow-unrelated-histories flag
>  - merge-tree: allow `ls-files -u` style info to be NUL terminated
>  - merge-tree: provide easy access to `ls-files -u` style info
>  - merge-tree: provide a list of which files have conflicts
>  - merge-ort: provide a merge_get_conflicted_files() helper function
>  - merge-tree: support including merge messages in output
>  - merge-ort: split out a separate display_update_messages() function
>  - merge-tree: implement real merges
>  - merge-tree: add option parsing and initial shell for real merge function
>  - merge-tree: move logic for existing merge into new function
>  - merge-tree: rename merge_trees() to trivial_merge_trees()
>  - Merge branch 'en/remerge-diff' into en/merge-trees
>
>  A new command is introduced that takes two commits and computes a
>  tree that would be contained in the resulting merge commit, if the
>  histories leading to these two commits were to be merged, and is
>  added as a new mode of "git merge-tree" subcommand.
>
>  Will merge to 'next'.
>  source: <pull.1122.v6.git.1645602413.gitgitgadget@gmail.com>

Let's wait. The extra data needed to handle Dscho's usecase might still suggest an output format change, and the command is intended to be plumbing-ish, so I'd like a bit more time to make sure we've got the format we want. Also, his comment/suggestion about -z affecting "Informational Messages" section is also interesting and might be worth doing even if it doesn't provide all the things Dscho wants for his usecase.

Previous: Junio C HamanoNext: Elijah Newren
Message 2 of 11 in “What's cooking in git.git (Feb 2022, #07; Fri, 25)”
  1. Junio C HamanoFeb 26, 2022
  2. en/merge-tree (Was: Re: What's cooking in git.git (Feb 2022, #07; Fri, 25))Elijah Newren, Feb 26, 2022
  3. en/present-despite-skipped (Was: Re: What's cooking in git.git (Feb 2022, #07; Fri, 25))Elijah Newren, Feb 26, 2022
  4. Johannes SchindelinMar 7, 2022
  5. Tao KlerksFeb 28, 2022
  6. Ævar Arnfjörð BjarmasonFeb 28, 2022
  7. Tao KlerksMar 1, 2022
  8. Junio C HamanoMar 1, 2022
  9. Tao KlerksMar 1, 2022
  10. ds/commit-graph-gen-v2-fixes (was Re: What's cooking in git.git (Feb 2022, #07; Fri, 25))Derrick Stolee, Feb 28, 2022
  11. ab/test-lib-tweaks (was: What's cooking in git.git (Feb 2022, #07; Fri, 25))Ævar Arnfjörð Bjarmason, Feb 28, 2022

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.