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

Re: [BUG] - git rebase -i performs rebase when it shouldn't?

From
ESEugene Sajine <euguess@gmail.com>
Date
Apr 13, 2010, 16:30 UTC
Message-ID
<p2l76c5b8581004130930rf5558655n4bb1f6d0c659498d@mail.gmail.com>
In-Reply-To
<4BC3407C.10701@viscovery.net>
Show 22 quoted lines
>
>> Come on! Please, please, explain me why it behaves DIFFERENTLY:
>>
>> esajine@ESAJINEWWW /c/git_repos/test2 (topic)
>> $ git rebase --onto master topic
>> First, rewinding head to replay your work on top of it...
>> fatal: Not a range.
>> Nothing to do.
>>                 <======== topic..HEAD is not a range, agreed
>>
>>
>> esajine@ESAJINEWWW /c/git_repos/test2 (topic)
>> $ git rebase -i --onto master topic
>> Successfully rebased and updated refs/heads/topic. <=== BUG – here it
>> printed me “noop” in file to edit, when I exited it should do nothing,
>> but it still did something and I double checked it.
>
> A historical accident, so to say. The implementor of interactive rebase
> felt the "noop" behavior was useful, and I agree, FWIW.
>
> -- Hannes
>

IMHO this "noop" behavior seems to be identical to "git reset --hard master" - the result is the same. Frankly, I don't understand what is useful in such thing being HIDDEN in "incorrect call" of interactive rebase...

Thanks, Eugene

Previous: Johannes SixtNext: Johannes Sixt
Message 18 of 19 in “[BUG] - git rebase -i performs rebase when it shouldn't?”
  1. Eugene SajineApr 9, 2010
  2. Jeff KingApr 10, 2010
  3. Junio C HamanoApr 10, 2010
  4. Jeff KingApr 10, 2010
  5. Johannes SixtApr 10, 2010
  6. Jeff KingApr 11, 2010
  7. Johannes SixtApr 11, 2010
  8. Jeff KingApr 12, 2010
  9. Michal VitecekApr 12, 2010
  10. Johannes SixtApr 12, 2010
  11. Eugene SajineApr 10, 2010
  12. Jeff KingApr 11, 2010
  13. Eugene SajineApr 11, 2010
  14. Eugene SajineApr 12, 2010
  15. Johannes SixtApr 12, 2010
  16. Eugene SajineApr 12, 2010
  17. Johannes SixtApr 12, 2010
  18. Eugene SajineApr 13, 2010
  19. Johannes SixtApr 14, 2010

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.