Missing diff option

[TBOpen]

The feature I liked the most of the old system was the ability to diff through the versions particularly when trying to find when something was changed. While I like the layout of the new system since you can fit a bunch more versions, it's not usable to me without the diff feature.

Thanks.

[pokazef]

Thanks for the report. To follow through on your idea, it might be nice to be able to leverage git and expose the "git blame" feature through the UI. That would allow one to find when something was changed much more easily.

[karanborawake]

diff option was the only reason I loved the old system.

[ADAMSCHUMAN]

diff option in old system was extremely helpful for backporting features

[michaelopdenacker]

Hello,

On 05/11/2018 06:01 PM, ADAMSCHUMAN wrote: diff option in old system was extremely helpful for backporting features

Thanks for voting for this feature. You're not the only one requesting it :) We will see what we can do to have it again... Cheers, Michael.

…

-- Free Electrons becomes Bootlin Details on https://bootlin.com/blog/free-electrons-becomes-bootlin/ Michael Opdenacker, CEO, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com

[michaelopdenacker]

Here is an example from an old LXR website:
http://tomoyo.osdn.jp/cgi-bin/lxr/diff/init/main.c?diffval=linux-5.3.18;diffvar=v

[standamo]

Was there any progress on this one?

[mnicuda]

👍 Another upvote from me - diff is crucial. Not git blame - I'm looking for all changes in a file between selected versions.

[tleb]

I do agree this is a good feature idea which can be useful to many. Questions to bring the discussion forward:

1. What did the old LXR look like? Links above are broken.
2. Should it be the straight forward solution of git diff -U1000000 piped into Pygments?
   • It implies we lose all language highlighting. Can we do better?
   • If we do that, we should have our filters be clever about the diff format and avoid highlighting the diff-specific keywords.
3. Or we could use something pre-existing?
   • diff2html
   • cgit can do a side-by-side but it does not highlight source code. Example.
   • This random issue talks about doing diffing on top of pygments. One response is a unified diffing AFTER applying pygments on both. It is pretty.
   • Forgejo has some pretty side-by-side or unified. It can do highlighting of the language. Random example.
   • Sourcehut is a good example in a simple approach: it only does unified diff, without language highlighting.
   • Anything else? Licenses will have to be checked.

[fstachura]

Should it be the straight forward solution of git diff -U1000000 piped into Pygments?

I would assume you want to have identifier links in the diff. The problem is, which version should the links refer to? Removed lines to the old version, added lines to the new version? What about the rest?