Bug 10577 - git submodules show up as "Delete" in VersionControl->Review Changes summary
Summary: git submodules show up as "Delete" in VersionControl->Review Changes summary
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Version Control ()
Version: 4.0
Hardware: PC Linux
: --- normal
Target Milestone: master
Assignee: Marius Ungureanu
URL:
Depends on:
Blocks:
 
Reported: 2013-02-22 07:33 UTC by Andres G. Aragoneses
Modified: 2015-08-20 03:23 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED FIXED

Description Andres G. Aragoneses 2013-02-22 07:33:54 UTC
Steps to reproduce:
1) Clone a git repo that has git submodules.
2) Don't init the submodules. (This is not a step you must do, but a step you shouldn't do ;) )
3) Open solution in MD.
4) Do some code change in the repo.
5) Right-click on solution -> Version Control -> Review changes.

Current results:
The submodule shows up with a "Delete" status.

Expected results:
Submodule should not show up, since no changes were made to it.
Comment 1 Andres G. Aragoneses 2013-02-22 07:34:46 UTC
Oh, just realised that this may be a dupe of bug 3823.
Comment 2 Lluis Sanchez 2013-06-27 06:08:17 UTC

*** This bug has been marked as a duplicate of bug 3823 ***
Comment 3 Andres G. Aragoneses 2013-12-05 18:46:40 UTC
Given that bug 3823 has been marked as NORESPONSE, when the steps to reproduce here still show a bug, then I'm reopening this bug (because I have no permissions to reopen bug 3823).
Comment 4 Marius Ungureanu 2014-09-08 00:14:14 UTC
Fixed in libgit2 branch.