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

Re: [PATCH] Document 'stash clear' recovery via unreachable commits

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
Aug 9, 2009, 09:26 UTC
Message-ID
<2e24e5b90908090226r1941c383j40853fd811ae3a73@mail.gmail.com>
In-Reply-To
<7veirlbwws.fsf@alter.siamese.dyndns.org>
2009/8/9 Junio C Hamano <gitster@pobox.com>
>
> Thomas Rast <trast@student.ethz.ch> writes:
Show 8 quoted lines
>
> > Unless you have merges of branch names containing WIP, or edit your
> > merge messages to say WIP, there will be no false positives.
>
> That may be true, but I suspect that people's stash entries that are worth
> saving are given their own messages with "git stash save 'message'" and do
> not necessarily say WIP.  I wish if there were a better way to identify
> them, but I do not think of any offhand.
gitk $(git fsck | grep commit | cut -f3 -d' ') --since='1 week ago'
The --since clause limits the display to stashes lost recently; adjust to taste.

A "stash" has a very recognisable, triangular, shape in the commit DAG -- with gitk you can visually find stashes really fast even if your time limit is too broad or you have too many other kinds of unreachable commits perhaps due to too many rebase etc.

Previous: Björn Steinbrink
Message 4 of 4 in “Document 'stash clear' recovery via unreachable commits”
  1. Document 'stash clear' recovery via unreachable commitsThomas Rast, Aug 9, 2009
  2. Junio C HamanoAug 9, 2009
  3. Björn SteinbrinkAug 9, 2009
  4. Sitaram ChamartyAug 9, 2009

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.