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

Re: [BUG] rebase --onto doesn't abort properly

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 6, 2014, 18:44 UTC
Message-ID
<xmqqha9hhrvz.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CALkWK0mEN=LjWKKdWznCXk5YwRQXVDPwtxUvVJnrG9zPPvH-Rw@mail.gmail.com>
Ramkumar Ramachandra <artagnon@gmail.com> writes:
Show 10 quoted lines
> Hi,
>
> On the latest git, I noticed that a rebase --onto doesn't abort
> properly. Steps to reproduce:
>
>   # on some topic branch
>   $ git rebase --onto master @~10
>   ^C # quickly!
>   $ git rebase --abort
>   # HEAD is still detached

I do not think --abort was designed to abort an uncontrolled stop like ^C in the first place. To allow that kind of "recovery", you need to teach "rebase" to first record the state you would want to go back to before doing anything, but then what happens if the ^C comes when you are still in the middle of doing so?

Previous: Ramkumar RamachandraNext: Ramkumar Ramachandra
Message 2 of 3 in “[BUG] rebase --onto doesn't abort properly”
  1. Ramkumar RamachandraJan 6, 2014
  2. Junio C HamanoJan 6, 2014
  3. Ramkumar RamachandraJan 6, 2014

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.