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

rebase --onto might "loose" commits

From
Björn Steinbrink <b.steinbrink@gmx.de>
Date
Feb 19, 2008, 07:23 UTC
Message-ID
<20080219072359.GA752@atjola.homenet>
Hi,

when there's nothing to rebase (ie. upstream..branch is empty), rebase fails to find any commits to rebase and correctly says "Nothing to do", but when --onto is given, we already did a "reset --hard" to newbase, so it already _did_ something.

As rebase also shows a "fatal: Not a range", during the operation, I assume that this is an actual bug and not just a plain user error.

A test script is attached.

Thank, Björn

Next: Johannes Schindelin
Message 1 of 4 in “rebase --onto might "loose" commits”
  1. Björn SteinbrinkFeb 19, 2008
  2. Johannes SchindelinFeb 19, 2008
  3. Björn SteinbrinkFeb 19, 2008
  4. Nicolas PitreFeb 19, 2008

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.