Re: make git diff output easier to read - use better diff heuristics

On Tue, Feb 13, 2018 at 7:25 PM, Σπύρος Βαζαίος wrote: > While I din't have the experience to express an opinion on this > matter, I have to say that the --no-indent-heuristic that Jeff > suggested worked great. > There were more than a handful of cases that this issue

Re: make git diff output easier to read - use better diff heuristics

Hi guys, While I din't have the experience to express an opinion on this matter, I have to say that the --no-indent-heuristic that Jeff suggested worked great. There were more than a handful of cases that this issue happened in my diff file (all were the same: #endif followed by #ifdef). Oh, and

Re: make git diff output easier to read - use better diff heuristics

On Tue, Feb 13, 2018 at 8:08 AM, Jeff King wrote: > On Tue, Feb 13, 2018 at 05:06:15PM +0200, Σπύρος Βαζαίος wrote: > >> Hi, I've came across an issue when using the git diff command. In >> particular the diff is different to what the svn diff produces. While >> both being correct

Re: make git diff output easier to read - use better diff heuristics

On Tue, Feb 13, 2018 at 05:06:15PM +0200, Σπύρος Βαζαίος wrote: > Hi, I've came across an issue when using the git diff command. In > particular the diff is different to what the svn diff produces. While > both being correct the output of the svn diff is easier to understand > than the git diff

make git diff output easier to read - use better diff heuristics

Hi, I've came across an issue when using the git diff command. In particular the diff is different to what the svn diff produces. While both being correct the output of the svn diff is easier to understand than the git diff one. See the following issue on github where I initially reported the