Am 10/19/2011 18:33, schrieb Jeff King: > git init > seq 1 5000 >foo > git add foo > git commit -m initial > sed -i '/^2..$/d' foo > seq 200 299 >>foo > git commit -a -m 'move 200-299 to end' > > I get the expected result from "git blame -M" (i.e., everything > attributed to the root commit). I see. My example is more like this: for i in `seq 1 20`; do md5sum - <<< $i; done > foo git commit -a -m foo for i in `seq 1 20`; do md5sum - <<< $i; done | sort > foo git commit -a -m foo\ sorted i.e., the sort order of a block of lines was changed "in place". Here, most of the lines are attributed to the last commit. Am I expecting too much from git-blame to detect line motions in such a case? -- Hannes -- 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