After spending an hour writing and testing a new test case for GIT I do the foolish: $ git add t/t1400-update-ref.sh # Hmm, maybe I should amend this into the prior commit. $ git format-patch -o .. next $ git reset --hard $ git update-ref HEAD~1 # Uhhohh... $ ls t/t1400-update-ref.sh All I can say is I'm very happy that update-index does a lot more than just update the index. I was easily able to find the deleted test by finding the most recently modified object in my .git/objects directory and pulling it back out with git cat-file. :-) Oh, and I totally agree with that discussion about GIT not clobbering files the user is working on which the user can't easily recover. I just wish recovery from the above stupidity didn't require going through .git/objects looking for the newest file. :-) Yes, I know that git reset --hard was brutal and yes, I didn't really need to use git-update-ref when git-reset would have also done the job for me. Arrgh. Its early and I wasn't thinking. -- Shawn. - : 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