On Sunday, April 23, 2017 at 6:26:57 PM UTC+3, Konstantin Khomoutov wrote: > Even if the issue the OP is facing will evoke nothing more than > rehashing of the old argument about the (un)expected semantics, it > might result in documentation patches. ;-)
I could just add to that argument that this issue is certainly looks like a logical inconsistency to an average user. The git operations are checking an index entry for the file in working tree but they doesn't fill that entry in the first place. Shouldn't this be considered as a kind of uninitialized pointer problem? And there is that useful abstraction that --hard should include --mixed semantics. -- 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 git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
