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

Stashes and expiring reflogs

From
JWJames Widman <widman@gimpel.com>
Date
Apr 6, 2010, 21:07 UTC
Message-ID
<loom.20100406T225419-205@post.gmane.org>
Hi all,
When I read this:
       "The latest stash you created is stored in refs/stash; older
       stashes are found in the reflog [...]"

... in the man page for git-stash, I started to feel a bit concerned, because this seems to imply that old stashes could be pruned. But I couldn't find any discussion on this issue in the documentation. I eventually found this thread:

http://thread.gmane.org/gmane.comp.version-control.git/84665

... which was enlightening, but didn't really give me a clue as to what the intended behavior is for the current version (1.7.0.4). Nanako presented a possible solution here:

http://article.gmane.org/gmane.comp.version-control.git/85055
... but it does not seem to have been merged into the current version.

Even if that isn't adopted, it would be good for the documentation to be clear about whether old stashes can be silently pruned. I would offer to write the documentation patch myself, but I would need direction from someone, and it would probably take them less time to just write it themselves. (:

Message 1 of 1 in “Stashes and expiring reflogs”
  1. James WidmanApr 6, 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.