Re: Unexpected behaviour with git stash save --keep-index?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Tue, Sep 02, 2008 at 01:14:10AM +0200, Jonas Flodén wrote:
> while I was using StGit for the first time and used git stash to split
> the changes into different patches I noticed that git stash save -- 
> keep-index
> will stash also the changes that are already in the index. This was  
> unexpected
> atleast to me but maybe someone can explain why it's correct.
A plain 'git stash [save]' means "save all local modifications and
clear both the index and the working tree".

'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".

> 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.

(Heh, I have just looked that section up, and noticed that the
formatting is broken and some comments are missing from the man page.
I will send out a patch in a minute.)

Regards,
Gábor

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux