We use a git mirror of m-c to generate blame data, and git doesn't store file moves explicitly like hg does. Presumably you used the `-f` to `hg mv` to make it explicitly realize this is a file move, despite a large diff between the two versions. The large diff probably results in git not recognizing it as a file move either. Proabably if we regenerated the blame repo with different parameters for the file copy/move detection [here](https://searchfox.org/mozilla-central/rev/227f5329f75bd8b16c6b146a7414598a420260cb/dom/ipc/BrowserParent.cpp#3156) we could correct this. I do plan on regenerating the blame repo at some point to fix bug 1431906 so maybe I can experiment with better parameters at that point.
Bug 1559145 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We use a git mirror of m-c to generate blame data, and git doesn't store file moves explicitly like hg does. Presumably you used the `-f` to `hg mv` to make it explicitly realize this is a file move, despite a large diff between the two versions. The large diff probably results in git not recognizing it as a file move either. Proabably if we regenerated the blame repo with different parameters for the file copy/move detection we could correct this. I do plan on regenerating the blame repo at some point to fix bug 1431906 so maybe I can experiment with better parameters at that point.