Re: possible gitattributes eol bug with new eol=crlf | lf support?

From: Eyvind Bernhardsen <eyvind.bernhardsen@gmail.com>
Date: Sep 12, 2010, 11:46 UTC
Message-ID: <4F27AD7B-2B2D-4378-B1D5-6F380396E0FF@gmail.com>
In-Reply-To: <AANLkTi=xPpPZzUqVEHEkH2sKvSVZH+MzunET6vEA_tw5@mail.gmail.com>

On 10. sep. 2010, at 23.27, Robert Buck wrote:

> I don't understand the inner workings of .git/index, but is removing
> that file destructive to history or anything? What are the
> implications of that delete-command?

Removing the index will lose the changes you've staged ("git add"ed) for the next commit, but your working directory won't be touched.  If you've added a file and then modified or deleted it, you would lose the version of that file that was in the index.

"git reset" then rebuilds the index identically to the HEAD commit, but without the staged changes and (importantly) the stat cache.  The point is to make git re-check every file to see if it has been modified.

Sorry, I should have mentioned the downsides.

- Eyvind