Re: "git reset" and newly created files.

From: Sam Ravnborg <sam@ravnborg.org>
Date: Aug 21, 2005, 21:46 UTC
Message-ID: <20050821214605.GA4134@mars.ravnborg.org>
In-Reply-To: <7vbr3rccjc.fsf@assigned-by-dhcp.cox.net>

Show 14 quoted lines

> 
> So you would naturally be tempted to do this:
> 
>     ... Re-edit, compile, and test.  This time it is perfect.
>     $ git commit -a -C ORIG_HEAD
> 
> Well, not really.  You can lose any file newly created in
> ORIG_HEAD this way.  Instead, you need to do this:
> 
>     ... Re-edit, compile, and test.  This time it is perfect.
>     $ git add <whatever file you have changed>
>     $ git commit -a -C ORIG_HEAD
> 
> Do people find this a big problem?

I often do some maybe not that brilliant changes in my tree, and when I then ask git to reset these I expect git to reset everything.

After a git-reset HEAD^ I really expect git to have rewinded back till where I started with no files added whatsoever.

>From the matter of least suprise git should not remember files added,

one have to do that by themself again if needed.

Sam