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

Re: stashing only unstaged changes?

From
RReto <reto@labrat.space>
Date
Jun 24, 2022, 08:16 UTC
Message-ID
<20220624081615.zhurjajwuvtvzs2y@feather>
In-Reply-To
<20220621142618.239b02cd@bigbox.attlocal.net>
You should be using proper branches, not stash.
Here's an email with some background from Junio:
https://lore.kernel.org/git/xmqq5ylior3l.fsf@gitster.g/
Some quotes:
> The intended use of "stash" is to clear the deck as quickly as
> possible to deal with "emergencies"
> Users are better off doing any large scale "I made a mess in the
> working tree with mixed changes, and I want to take time to separate
> them out" on separate (possibly temporary) branches, instead of
> using "stash save" + "stash pop"
In other words, you are using the wrong tool for the job probably.

Cheers, Reto

Previous: Tim ChaseNext: Tim Chase
Message 2 of 10 in “stashing only unstaged changes?”
  1. Tim ChaseJun 21, 2022
  2. RetoJun 24, 2022
  3. Tim ChaseJun 24, 2022
  4. Konstantin KhomoutovJun 24, 2022
  5. Erik Cervin EdinJun 24, 2022
  6. Tim ChaseJun 24, 2022
  7. Ævar Arnfjörð BjarmasonJun 24, 2022
  8. Erik Cervin EdinJun 24, 2022
  9. Ævar Arnfjörð BjarmasonJun 24, 2022
  10. Junio C HamanoJun 24, 2022

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.