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.
NGit has a bug where the 'Length' of a submodule as stored in the git repository is different to the 'Length' of the submodule on disk. As such, it always shows up as modified if you do a 'Review Status' call.
The issue is in WorkingTreeIter.CompareMetadata where the following call fails:
if (!entry.IsSmudged && (GetEntryLength() != entry.Length))
There is no readily apparent way for me to fix this. I believe NGit should probably be altered to ignore submodules when doing a git status, similar to what git does.
*** Bug 10577 has been marked as a duplicate of this bug. ***
This is no longer an issue from what I noticed.
I still can reproduce this bug (at least with the steps to reproduce explained in the duped bug 10577).
A fix for this has been issued in master for MD. Submodules are automatically init-ed on a repository clone.
When I wrote comment#3, I was referring to master.
Bug 10577 is not about the scenario when the user does a clone with MonoDevelop, but a manual clone.
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
I think you can put this back to NEW|CONFIRMED.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.
>This bug has not been changed from the NEEDINFO state since my previous
>comment, marking as RESOLVED NORESPONSE.
Well, I don't have permissions to change the state, otherwise I would have changed it. PJ: did you at least read my comment #7?
>Please feel free to REOPEN this bug at any time if you are still experiencing
>the issue. Please add the requested information and set the bug back to the NEW
>(or CONFIRMED) state.
As I don't have permissions to REOPEN this bug, then I've just REOPENED bug 10577 FYI.