On di, 2015-06-02 at 23:48 -0700, Junio C Hamano wrote: > > I am kind of surprised after reading these two threads that my > take on this issue has changed over time, as my knee-jerk > reaction before reading them was the opposite, something > along the lines of "This is only immediately after 'git init'; why > bother?". Or depending on my mood, that "How stupid do you > have to be..." sounds exactly like a message I may advocate > for us to send. Perhaps I grew more bitter with age. The "fatal: Failed to resolve 'HEAD' as a valid ref." message, closely related to the "fatal: bad default revision 'HEAD'" message that started this thread just came by in #git with the following situation: $ git init $ git add . # Oops, didn't want to add foo.xyz $ git reset foo.xyz fatal: Failed to resolve 'HEAD' as a valid ref. The solution there is simple, git rm --cached, but I think git could produce more helpful messages when a repo is empty. I think you are growing bitter with age ;) -- Dennis Kaarsemaker www.kaarsemaker.net -- 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