git reset --hard and uncommitted files in index

Hi,

Today I was working on a script that modify many files on a repository, therefore during testing phase I needed to reset --hard to get back to the last commit. This operation does not affect untracked files.

Since i was going to commit the script, at some point I decided to add it to the index so I could track/revert changes to it. On the next reset Git deleted the script.

Fortunately "git add" creates an object that I could easily recover (thanks to wereHamster on #git for pointing that out), however I was wondering if it's really the desired behavior to *delete* a file that have been added to the index but isn't on the previous commit? Shouldn't git just unstage it?

-- Thomas