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

en/merge-tree (Was: Re: What's cooking in git.git (Jun 2022, #07; Wed, 22))

From
Elijah Newren <newren@gmail.com>
Date
Jun 22, 2022, 21:16 UTC
Message-ID
<CABPp-BGGDvZ40TY939fFM0xPZuaogPS+ymfEpc+hv-sJnO8Jcg@mail.gmail.com>
In-Reply-To
<xmqq7d584hqb.fsf@gitster.g>
On Wed, Jun 22, 2022 at 12:41 PM Junio C Hamano <gitster@pobox.com> wrote:
Show 25 quoted lines
> [Stalled]
>
> * 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.
>
>  On hold.
>  cf. <CABPp-BGZ7OAYRR5YKRsxJSo-C=ho+qcNAkqwkim8CkhCfCeHsA@mail.gmail.com>
>  source: <pull.1122.v6.git.1645602413.gitgitgadget@gmail.com>

Can you update from "On hold" to "new patchset exists" (new source: <pull.1122.v7.git.1655511660.gitgitgadget@gmail.com>) and move it out from the stalled section?

(Also, FWIW, v7 was collaborative effort between Dscho and I, and we're now finally both pretty happy with the state of the patches, as noted over at https://lore.kernel.org/git/CABPp-BFfRGQybYManC6LfFTaAd3mweBxL=APCGP_vRF-WQxGSw@mail.gmail.com/).

Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 13 in “What's cooking in git.git (Jun 2022, #07; Wed, 22)”
  1. Junio C HamanoJun 22, 2022
  2. en/merge-tree (Was: Re: What's cooking in git.git (Jun 2022, #07; Wed, 22))Elijah Newren, Jun 22, 2022
  3. Junio C HamanoJun 22, 2022
  4. Johannes SchindelinJun 23, 2022
  5. ab/test-without-templates (was: What's cooking in git.git (Jun 2022, #07; Wed, 22))Ævar Arnfjörð Bjarmason, Jun 23, 2022
  6. Junio C HamanoJun 23, 2022
  7. Ævar Arnfjörð BjarmasonJun 27, 2022
  8. Junio C HamanoJun 27, 2022
  9. Ævar Arnfjörð BjarmasonJun 27, 2022
  10. hx/unpack-streaming (was: What's cooking in git.git (Jun 2022, #07; Wed, 22))Ævar Arnfjörð Bjarmason, Jun 23, 2022
  11. Junio C HamanoJun 23, 2022
  12. gc/submodule-update (was Re: What's cooking in git.git (Jun 2022, #07; Wed, 22))Glen Choo, Jun 24, 2022
  13. Junio C HamanoJun 24, 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.