Bug: Git GUI "No differences detected"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi, I want to ask you about a bug that Git has had for years. It's
tracked on pages like
https://stackoverflow.com/questions/57556917/git-gui-no-diffferences-detected
but I still haven't been able to find a solution to prevent this from
occurring.

Problem:
Git GUI shows a "No differences detected" popup when clicking on a
file, and it returns back to the same state after closing the popup.
When I do `git status`, the file is listed there, but `git diff` (with
any line-ending-related switches inspired by stackoverflow) doesn't
show anything for the file.

Cause:
I assume it's typically due to LF/CRLF changes.

Workaround:
Manually add the file, which makes the diff disappear.

Complaint:
It's extremely annoying to click so many times on GUI for every such
file. Files have to be frequently added just to satisfy the status
check, really disrupting your workflow when preparing commits and
reviewing diffs one by one.

Attempted settings:
I tried all the autocrlf options, and even fileMode (though I'm on
Windows); nothing helps to remove the file from status...

Reasons triggering the symptom:
I have some application that periodically modifies tracked files in
some way, causing this issue to regularly re-appear for the same set
of files. Over the years, I had it happen from various sources, it's
one of the issues that follows you the entire life...

Request:
It needs to be recognized as a frequently occurring bug that doesn't
have a permanent solution yet. It should be fixed either on the Git
GUI side by automatically hiding these files (or at least hiding the
annoying pop-up), or the git status itself could recognize that the
file has in fact not changed. If there is any actual change in the
line endings, its diff should be displayed, because that would be
definitely an actual modification to the file, which we may want to
review and push upstream. The current design of hiding CR/LF changes
from a user is flawed anyway.

Thanks, I'm really hoping this can be officially tracked and reported
on; a reliance on StackOverflow articles as an issue tracker is
insufficient and hides our sentiment of how many hours of productivity
we're wasting on it.




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux