All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jonas Flodén" <jonas.floden@gmail.com>
To: git@vger.kernel.org
Subject: Re: Unexpected behaviour with git stash save --keep-index?
Date: Tue, 02 Sep 2008 08:20:13 +0200	[thread overview]
Message-ID: <g9ilut$n58$1@ger.gmane.org> (raw)
In-Reply-To: <20080902012804.GB6739@neumann>

SZEDER Gábor wrote:
 > 'git stash save --keep-index' means "save all local modifications and
 >  remove all modifications from the working tree that are not in the
 > index".  This differs substantially from "save only those
 > modifications that are not in the index, and then remove them from
 > the working tree".
 >

Thanks for the explanation. It seemed strange first but now I know
why it does that.

 >> Also maybe someone could someone recommend a way to split an
 >> unclean working dir into several patches/commits?
 > The workflow described at the end of stash's man page (under 'Testing
 >  partial commits') works well for me.
 >

Thanks. What about the case when I already have a number of existing
patches/commits and want to split the working dir into them.

Regards,
Jonas

  parent reply	other threads:[~2008-09-02  6:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01 23:14 Unexpected behaviour with git stash save --keep-index? Jonas Flodén
2008-09-02  1:28 ` SZEDER Gábor
2008-09-02  1:35   ` [PATCH] Documentation: fix disappeared lines in 'git stash' manpage SZEDER Gábor
2008-09-02  1:45     ` [PATCH] Documentation: minor cleanup in a use case in 'git stash' manual SZEDER Gábor
2008-09-02  6:20   ` Jonas Flodén [this message]
2008-09-02  7:45 ` Unexpected behaviour with git stash save --keep-index? Karl Hasselström

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='g9ilut$n58$1@ger.gmane.org' \
    --to=jonas.floden@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.