Am 16.08.2012 10:42, schrieb Ed Willink:
Hi
My suspicion is that the problem is in the comparison tooling.
The files in the repo seem to be normalized to LF line endings, but some
Windows tooling creates CR-LF; some tools can
be fixed via Bugzillas but it's a losing battle.
I totally disagree. All these tools have been working fine with all other version control systems. And the false
positives in the staging view appear with no comparison tool being involved. And it's impossible to get rid of them by
means of the tool (EGit) that has created them.
I suspect that some of EGIT's comparisons are failing to perform a
pseudo-commit to normalize the line endings before
performing a comparison.
I have no clue what in EGit is wrong. But with the EGit team simply moving the problem reports to other projects it's
unlikely that the problem ever gets fixed.
[EGIT has no obvious counterpart of CVS's binary flag, so how does it know
which CR-LF byte pairs it is safe to normalize?]
Good question. I have no answer, though.
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
