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

git rebase --abort of an --onto run does not checkout the originating branch

From
Joshua Jensen <jjensen@workspacewhiz.com>
Date
Oct 22, 2010, 17:01 UTC
Message-ID
<4CC1C34E.8090203@workspacewhiz.com>

'git rebase --abort' has documentation stating it will restore the original <branch>. This works great for my basic usage of 'git rebase --interactive', for instance.

When running 'git rebase --onto', it does exactly what the documentation states, but the restored branch is not desirable.

To cherry pick a range of commits, I run:
git rebase --onto mybranch START_SHA END_SHA
In the middle, I decide to run 'git rebase --abort'.

Just as the documentation states, it performs a checkout of END_SHA as the restored branch. END_SHA has nothing to do with the originating branch, and confusion ensues.

Is there a reason why 'git rebase' should not store off the originating branch and use that for an --abort, instead of <branch> which is END_SHA?

Thanks.
Josh
Next: Junio C Hamano
Message 1 of 4 in “git rebase --abort of an --onto run does not checkout the originating branch”
  1. Joshua JensenOct 22, 2010
  2. Junio C HamanoOct 22, 2010
  3. Joshua JensenOct 28, 2010
  4. Jakub NarebskiOct 28, 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.