Здравствуйте, Junio. Вы писали 8 апреля 2015 г., 5:48:36: JCH> KES <kes-kes@xxxxxxxxx> writes: >> **UPDATE:** Short answer >> `git blame` follow renames but not for `git blame COMMIT^ -- <filename>` JCH> Suppose you have file A and file B in your version v1.0. .... As it does not make any sense to tell C to Git and JCH> then magically make it guess you meant A in some cases and B in some JCH> other. If v1.0 did not have C, the only sensible thing to do is to JCH> exit instead of making a guess (and without telling the user how it JCH> guessed). I agree with your complex example. 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. `git blame COMMIT^ -- C` For complex example the clue will be if user supply line number he want to blame. So if user supply line 10 we follow A, if user supply 30 we follow B. Simple and great =) (I mean usefull for people) `git blame --line 10 COMMIT^ -- C` `git blame --line 30 COMMIT^ -- C` -- С уважением, 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