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

Re: git stash save --keep-index

From
SRSverre Rabbelier <alturin@gmail.com>
Date
Jul 15, 2008, 14:50 UTC
Message-ID
<bd6139dc0807150750u1eff0389x9e4b61822032c65d@mail.gmail.com>
In-Reply-To
<20080715142615.GI8224@neumann>
On Tue, Jul 15, 2008 at 4:26 PM, SZEDER Gábor <szeder@ira.uka.de> wrote:
Show 9 quoted lines
> If there are unstaged changes in the worktree, then yes, 'git stash
> apply/pop' will error out complaining about dirty state.  However, if
> there are changes in the index, but no unstaged changes in the
> worktree, then apply/pop should work (assuming there are no conflicts,
> of course).
>
> So, you won't need that temporary commit, if you have not modified
> anything or have added all changes to the index since 'git stash
> save --keep-index'.
Mhhh, ok, I can live with that, thanks!
-- 
Cheers,

Sverre Rabbelier
Previous: SZEDER Gábor
Message 3 of 3 in “git stash save --keep-index”
  1. Sverre RabbelierJul 15, 2008
  2. SZEDER GáborJul 15, 2008
  3. Sverre RabbelierJul 15, 2008

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.