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

Should I try to fix rebase interactive preserve-merges bug

From
Wink Saville <wink@saville.com>
Date
Mar 25, 2018, 17:32 UTC
Message-ID
<CAKk8isqvfhiMPCdNBW5WNN4BfN1sLszekQscpy5M2Okh2YmbZg@mail.gmail.com>
There is a "TODO known breakage" in t3404-rebase-interactve.sh:
   not ok 24 - exchange two commits with -p # TODO known breakage

I'm contemplating trying to fix it. But with --recreate-merges coming maybe it's not worth the effort. Should I proceed with attempting a fix or is --preserve-merges going to be a synonym for --recreate-merges?

-- Wink
Next: Jacob Keller
Message 1 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.