For future reference, we need to set the `--break-rewrites` option or equivalent in order for git to detect this as a file rename. The reason is that the browser.xhtml file existed already, and so git treats that file as "modified" rather than "added" and so it doesn't treat that file as a destination for copies/renames. By using `--break-rewrites` the self-similarity of browser.xhtml is high enough that the "modified" gets broken into an "delete/add" pair and the "add" half of that can get matched with the browser.xul "delete" to form a rename pair.
Bug 1559145 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
For future reference, we need to set the `--break-rewrites` option or equivalent in order for git to detect this as a file rename. The reason is that the browser.xhtml file existed already, and so git treats that file as "modified" rather than "added" and so it doesn't treat that file as a destination for copies/renames. By using `--break-rewrites` the self-similarity of browser.xhtml is low enough that the "modified" gets broken into an "delete/add" pair and the "add" half of that can get matched with the browser.xul "delete" to form a rename pair.