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

[PATCH] git stash: document apply's --index switch

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Sep 30, 2007, 22:30 UTC
Message-ID
<1191190557-24902-1-git-send-email-vmiklos@frugalware.org>
In-Reply-To
<Pine.LNX.4.64.0709302226270.28395@racer.site>
---
On Sun, Sep 30, 2007 at 10:29:05PM +0100, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Now that you know what --index is supposed to do, maybe you are nice
> enough to extend the documentation and post a patch?
something like this?
VMiklos
 Documentation/git-stash.txt |    7 ++++++-
 1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-stash.txt b/Documentation/git-stash.txt
index 05f40cf..5723bb0 100644
--- a/Documentation/git-stash.txt
+++ b/Documentation/git-stash.txt
@@ -63,7 +63,7 @@ show [<stash>]::
 	it will accept any format known to `git-diff` (e.g., `git-stash show
 	-p stash@\{1}` to view the second most recent stash in patch form).
 
-apply [<stash>]::
+apply [--index] [<stash>]::
 
 	Restore the changes recorded in the stash on top of the current
 	working tree state.  When no `<stash>` is given, applies the latest
@@ -71,6 +71,11 @@ apply [<stash>]::
 +
 This operation can fail with conflicts; you need to resolve them
 by hand in the working tree.
++
+If the `--index` option is used, then tries to reinstate not only the working
+tree's changes, but also the index's ones. However, this can fail, when you
+have conflicts (which are stored in the index, where you therefore can no
+longer apply the changes as they were originally).
 
 clear::
 	Remove all the stashed states. Note that those states will then
-- 
1.5.3.2.111.g5166-dirty
Previous: Johannes Schindelin
Message 6 of 6 in “suggestion for git stash”
  1. Bruno HaibleSep 30, 2007
  2. Junio C HamanoSep 30, 2007
  3. Matthieu MoySep 30, 2007
  4. Bruno HaibleSep 30, 2007
  5. Johannes SchindelinSep 30, 2007
  6. git stash: document apply's --index switchMiklos Vajna, Sep 30, 2007

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.