Community
Participate
Working Groups
With core.autocrlf=true, text files having the executable bit set are considered modified when the index version contains CR-LF line endings. This is fall-out from commits * https://git.eclipse.org/r/#/c/127324/ : corrected handling a non-normalized index, but only for FileMode.REGULAR_FILE * https://git.eclipse.org/r/#/c/149390/ : removed an old work-around for non normalized index not being handled before The second change is correct; that work-around really isn't needed anymore. But the first change should also have considered FileMode.EXECUTABLE_FILE.
New Gerrit change created: https://git.eclipse.org/r/159980
See also https://www.eclipse.org/forums/index.php/t/1102934/ .
What is the approximate time frame for this change being available in a release?
(In reply to David M. Karr from comment #3) > What is the approximate time frame for this change being available in a > release? couple of weeks after fix was merged
Gerrit change https://git.eclipse.org/r/159980 was merged to [stable-5.6]. Commit: http://git.eclipse.org/c/jgit/jgit.git/commit/?id=24f82b533a1774f03fbedb5f32854aa8858fce6d
EGit nightly should have the fix for this. Update site at https://download.eclipse.org/egit/updates-nightly .