Здравствуйте, Junio. Вы писали 13 апреля 2015 г., 8:32:33: JCH> Eugen Konkov <kes-kes@xxxxxxxxx> writes: >> I agree with your complex example. JCH> Note that it is a norm, not anything complex, that we do not rename JCH> a file wholesale. >> But it will be great to guess in simple case, when in version v1.0 >> only one file A which were renamed into C half year later. JCH> So you used to have A and somebody renamed that into C in the past. JCH> The content of C in the current version is what you used to have in JCH> A. JCH> What should happen if you also have A, whose contents do not have JCH> any relation to that old A, in today's code? JCH> What should happen if you also used to have C, whose contents do not JCH> have any relation to that old A or current C? JCH> What happens if you added such random guessing and you were not so JCH> familiar with the project history to know these unrelated A's and JCH> C's that used to exist in the past? JCH> Current Git _consistently_ behaves, even in the presense of anything JCH> that can lead to confusing behaviour. When you ask JCH> git blame OLD -- A JCH> it does not matter if you have an unrelated A in the revision that JCH> you happen to have checked out in your working tree (i.e. HEAD). JCH> The above command line talks about the old revision OLD and A talks JCH> about the path A in that old revision. Yes. you are right. I do not think about these examples. -- С уважением, Eugen mailto:kes-kes@xxxxxxxxx -- 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