Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
MonoDevelop doesn't respect .gitattributes for line ending handling, which means that for projects that depend on it heavily, suxh as MD itself, it incorrectly shows many files as 100% modified. Changes to such files would be committed incorrectly, which is a major issue.
This is a limitation in NGit. Not fixable on our side, needs to be resolved upstream.
It depends on https://bugzilla.xamarin.com/show_bug.cgi?id=9917
Also added https://bugs.eclipse.org/bugs/show_bug.cgi?id=301775
It will be fixed when we merge ikvmJGit branch into master.
*** Bug 21437 has been marked as a duplicate of this bug. ***
Is this bug resolved? I am still getting this issue with Xamarin 5.1.4 (as per duplicate bug 21437).
This will come in a future release. we haven't yet switched to the new git provider.
I have checked this issue and observed that after commit, all changes is successfully updated to git.
Could you please let me know if I have to check anything else to verify this issue?
You need to:
1. Checkout a repository.
2. Modify files in it.
3. Verify that when opening the files and switching to the Changes panel at the bottom of the document, only the changed lines are colored, not the whole file.
I have recheck this issue as per comment#9 and Its working fine.
Hence closing this issue.