It looks like the parsing of git diff output is not robust enough so that it can be confused by the diff of a patch. See below on how to reproduce the bug.
Operation system: Debian Testing (2024-04)
Git version: 2.43.0
qgit version: Git HEAD (cf3350e88cc8c8249385efac63ddf15ac1eff42a 2024-02-03), built with cmake . ; make. The bug is also present with qgit 2.10
How to reproduce the bug
Decompress the attached tarball.
Open qgit in the extracted directory. View all history when opening.
In the Rev list page, click the row containing the upstream branch (aka tag upstream/1.2+git20230914).
In the file list on the bottom-right side, click the pref.js row.
The diff on the left side does not show the diff of pref.js file, which is the bug. Instead, it is showing diff of /debian/patches/set-gtk-3.0-to-prevent-importing-4.0.patch.
It looks like the parsing of
git diffoutput is not robust enough so that it can be confused by the diff of a patch. See below on how to reproduce the bug.cmake . ; make. The bug is also present with qgit 2.10How to reproduce the bug
qgitin the extracted directory. View all history when opening.upstreambranch (aka tagupstream/1.2+git20230914).pref.jsrow.pref.jsfile, which is the bug. Instead, it is showing diff of/debian/patches/set-gtk-3.0-to-prevent-importing-4.0.patch.Attached tarball
sample_ibus-avro.tar.xz.zip