I found out that "git reset --hard" produced different outcome depending on current index content, i.e. when there is no entry for a file in working tree it actually changed that file. While on the contrary, if you use "git reset --mixed" right before that, the file won't be touched. This affects make, which thinks that the file was changed. Is that intended? I found this behavior somewhat confusing and don't see it documented anywhere.
-- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
