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

Re: [bug] Stashes lost after out-of-memory situation

From
René Scharfe <l.s.r@web.de>
Date
Oct 25, 2020, 15:42 UTC
Message-ID
<22f34328-1e87-aa4b-3893-564dff1fb893@web.de>
In-Reply-To
<5a3db65b-1877-c5be-8077-2926637fba6e@virtuell-zuhause.de>
Am 25.10.20 um 13:27 schrieb Thomas Braun:
Show 13 quoted lines
> On 10/24/2020 7:06 PM, René Scharfe wrote:
>
> [...]
>
>> Looks like stash calls rev-parse to see if a
>> stash pop removed the last stash and in that case proceeds to delete the
>> stash ref and its reflog
>
> I was a bit suprised to learn that removing the last stash entry also
> removes it from the reflog.
>
> Wouldn't it be more convenient if it would be kept in the reflog even
> after popping?

The log of the stash ref is separate from the normal reflog. Popping a stash doesn't remove anything from the latter.

René
Previous: Thomas Braun
Message 4 of 4 in “[bug] Stashes lost after out-of-memory situation”
  1. Marek MrvaOct 23, 2020
  2. René ScharfeOct 24, 2020
  3. Thomas BraunOct 25, 2020
  4. René ScharfeOct 25, 2020

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.