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

tc/replay-linearize [Was: Re: What's cooking in git.git (Jul 2026, #05)]

From
Elijah Newren <newren@gmail.com>
Date
Jul 13, 2026, 21:34 UTC
Message-ID
<CABPp-BHFZsdNpYWEWq-r+BqKeFQ6uh1MAbSfWQRPL8-diw6NOA@mail.gmail.com>
In-Reply-To
<xmqqik6j1m7u.fsf@gitster.g>
On Sun, Jul 12, 2026 at 10:40 PM Junio C Hamano <gitster@pobox.com> wrote:
Show 12 quoted lines
>
> * tc/replay-linearize (2026-07-07) 3 commits
>   (merged to 'next' on 2026-07-09 at 371c2e9c3b)
>  + replay: offer an option to linearize the commit topology
>  + replay: resolve the replay base outside pick_regular_commit()
>  + replay: add helper to put entry into replayed_commits
>
>  The 'git replay' command has been taught the '--linearize' option to
>  drop merge commits and linearize the replayed history, mimicking 'git
>  rebase --no-rebase-merges'.
>
>  Will merge to 'master'.
Could we hold off on that until there's a response to
<CABPp-BGzU9KHGF1nipi2HZaa1AiikMKGGaapQzHVH06wO4V1ww@mail.gmail.com> ?
 I think the third patch has a pretty serious principle of least
astonishment violation, and there's two alternatives that weren't
previously considered -- one of which would be simple to implement.
Previous: Michael Montalbo
Message 3 of 3 in “What's cooking in git.git (Jul 2026, #05)”
  1. Junio C HamanoJul 13, 2026
  2. Michael MontalboJul 13, 2026
  3. tc/replay-linearize [Was: Re: What's cooking in git.git (Jul 2026, #05)]Elijah Newren, Jul 13, 2026

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.