Open jens-maus opened 8 years ago
Argh, that repo is huge, I don't have the patience to clone. Can you produce a minimal example repo?
Note that git diff
offers multiple algorithms, and the default may have changed with git version, so it is not so simple to use it as a gold standard.
But yes, in this case, it does not seems that the problem comes from an algorithm difference...
I've downloaded the 3 versions of ts/build/buid
, and I reproduce your diff locally.
The GitHub diff is too lines off (actual changes happen 2 lines above the lines shown on github diff)
Reproduced and minimized to a single 150 loc file, 2 commit, no merges repo: https://github.com/Thinstation/thinstation/commit/b6b8b13c4e22955d1cc022b53a07ed4d590d732e
There are no non-printable chars in that file:
tr -d '[[:print:]]\n' <1 | wc
If I try to bisect further it stops reproducing...
I came across a potential bug of the web-based diff tool in github where for one specific diff the web-based diff tool somehow shows something completely different (in fact a NOP) than using the cmd-line "git diff" which actually should be the gold standard.
See here: https://github.com/Thinstation/thinstation/commit/b6b8b13c4e22955d1cc022b53a07ed4d590d732e
Using cmd-line "git diff" for this commit show the following diff, however: