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

Re: Limitiations of git rebase --preserve-merges --interactive

From
Anatoly Borodin <anatoly.borodin@gmail.com>
Date
Sep 22, 2016, 21:04 UTC
Message-ID
<ns1h09$pjs$2@blaine.gmane.org>
In-Reply-To
<20160922194848.GB6641@ikke.info>
Hi Kevin,
Kevin Daudt <me@ikke.info> wrote:
> Changing the order, or dropping commits might then give unexpected
> results.

The question that Stefan has is rather "what is *supposed* to work / give *expected* results?". Some stuff can be found in the tests (t/t*rebase*preserve*), but maybe there is more?

-- 
Mit freundlichen Grüßen,
Anatoly Borodin
Previous: Stefan BellerNext: Anatoly Borodin
Message 8 of 15 in “Limitiations of git rebase --preserve-merges --interactive”
  1. Stefan HallerSep 20, 2016
  2. Anatoly BorodinSep 22, 2016
  3. Kevin DaudtSep 22, 2016
  4. Stefan BellerSep 22, 2016
  5. Stefan HallerSep 23, 2016
  6. Johannes SchindelinSep 23, 2016
  7. Stefan BellerSep 23, 2016
  8. Anatoly BorodinSep 22, 2016
  9. Anatoly BorodinSep 22, 2016
  10. Stefan BellerSep 22, 2016
  11. Johannes SchindelinSep 23, 2016
  12. Stefan HallerSep 23, 2016
  13. Junio C HamanoSep 23, 2016
  14. Stefan HallerSep 23, 2016
  15. Johannes SixtSep 23, 2016

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.