From: Elijah Newren <newren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: en/merge-tree (Was: Re: What's cooking in git.git (Feb 2022, #08; Mon, 28))
Date: Tue, 1 Mar 2022 17:26:00 -0800 [thread overview]
Message-ID: <CABPp-BGZ7OAYRR5YKRsxJSo-C=ho+qcNAkqwkim8CkhCfCeHsA@mail.gmail.com> (raw)
In-Reply-To: <xmqqmti9ssah.fsf@gitster.g>
On Tue, Mar 1, 2022 at 7:26 AM Junio C Hamano <gitster@pobox.com> wrote:
>
> * 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>
As I mentioned on the last "What's cooking", let's not. Please mark
it as expecting a reroll instead. I'm waiting to hear back from Dscho
on whether my latest proposal at [1] would solve his usecase. That
proposal suggests output format and various code changes.
[1] https://lore.kernel.org/git/CABPp-BGnqXdFBNAyKRXgvCHv+aUZTMg-CgcQf95dKAR-e1zSjQ@mail.gmail.com/
next prev parent reply other threads:[~2022-03-02 1:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 13:42 What's cooking in git.git (Feb 2022, #08; Mon, 28) Junio C Hamano
2022-03-01 14:26 ` ds/commit-graph-gen-v2-fixes (was Re: What's cooking in git.git (Feb 2022, #08; Mon, 28)) Derrick Stolee
2022-03-01 14:58 ` Patrick Steinhardt
2022-03-01 18:07 ` Junio C Hamano
2022-03-01 22:55 ` js/scalar-diagnose, was Re: What's cooking in git.git (Feb 2022, #08; Mon, 28) Johannes Schindelin
2022-03-02 7:05 ` Junio C Hamano
2022-03-02 1:26 ` Elijah Newren [this message]
2022-03-07 16:31 ` en/merge-tree (Was: Re: What's cooking in git.git (Feb 2022, #08; Mon, 28)) Johannes Schindelin
2022-03-08 8:30 ` Elijah Newren
2022-03-09 11:46 ` Johannes Schindelin
2022-03-03 16:11 ` ab/object-file-api-updates (was: " Ævar Arnfjörð Bjarmason
2022-03-03 22:23 ` ab/object-file-api-updates Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABPp-BGZ7OAYRR5YKRsxJSo-C=ho+qcNAkqwkim8CkhCfCeHsA@mail.gmail.com' \
--to=newren@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).