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

Re: Should I try to fix rebase interactive preserve-merges bug

From
Wink Saville <wink@saville.com>
Date
Mar 25, 2018, 20:22 UTC
Message-ID
<CAKk8isp_oFNRNbO0fSJx5GC_QKKiojsL=TxBJu2Z54xp5NCFDA@mail.gmail.com>
In-Reply-To
<CA+P7+xqqLU-J5hv=yioMxMvp40hz_S9GfimjE7bp1Pj_TP-k3w@mail.gmail.com>
Show 8 quoted lines
> AFAIK this breakage of preserve-merges is a design flaw which isn't
> really fixable, which is why --recreate-merges is being added.
>
> I believe the plan is to deprecate preserve-merges once
> recreate-merges has landed.
>
> Thanks,
> Jake
Txs for the info, hopefully others will respond.
Previous: Jacob KellerNext: Johannes Schindelin
Message 3 of 4 in “Should I try to fix rebase interactive preserve-merges bug”
  1. Wink SavilleMar 25, 2018
  2. Jacob KellerMar 25, 2018
  3. Wink SavilleMar 25, 2018
  4. Johannes SchindelinMar 26, 2018

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.