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

RE: bug: autostash is lost after aborted rebase

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
May 19, 2014, 01:38 UTC
Message-ID
<537960a5f0d95_10da88d308b6@nysa.notmuch>
In-Reply-To
<20140519005719.GB38299@tequila>
Karen Etheridge wrote:
Show 10 quoted lines
> 
> scenario: 
> - edit some tracked files; do not add them to the index
> - "git config rebase.autostash true"
> - "git rebase -i HEAD~3" (an autostash will be created)
> - delete the entire buffer and save/exit the editor - this will abort the
>   rebase
> 
> poof, the autostash is gone (it is not reapplied) -- it must be explicitly
> applied again via the SHA that was printed earlier.

Yeah, I noticed this issue while rewriting `git rebase` in Ruby. I also noticed many other issues and inconsistencies that happen depending on what arguments you pass to `git rebase`.

I'm in the process of writing a much more improved and consistent `git rebase` in Ruby with a different interface. Sadly it's still not ready.

> (please cc me; I am not subscribed to the list.)

No need to say that, only on mailing lists that do Reply-To munging, and Git is not one of them.

Cheers.
-- 
Felipe Contreras
Previous: Karen EtheridgeNext: Matthieu Moy
Message 2 of 6 in “bug: autostash is lost after aborted rebase”
  1. Karen EtheridgeMay 19, 2014
  2. Felipe ContrerasMay 19, 2014
  3. Matthieu MoyMay 19, 2014
  4. Junio C HamanoMay 20, 2014
  5. Eugene YarmashMay 16, 2016
  6. Philippe VaucherMay 19, 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.