This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 231605

Summary:	Git repository cannot commit submodule's updated version, to track the new version
Product:	versioncontrol	Reporter:	naitsirch <naitsirch>
Component:	Git	Assignee:	Ondrej Vrabec <ovrabec>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	git
Priority:	P3
Version:	7.3.1
Hardware:	PC
OS:	Windows 7
Issue Type:	DEFECT	Exception Reporter:
Attachments:	Screenshot of the differences between cmd and Netbeans submodule handling Screenshot of the differences between cmd and Netbeans submodule handling

Description naitsirch 2013-06-21 07:43:02 UTC

Created attachment 136110 [details]
Screenshot of the differences between cmd and Netbeans submodule handling

Hi.
I am working with a git repository which contains the symfony framework. One of the bundles (the "FutarBundle") is organized as a submodule.

Please look at the attached screenshot for better understanding.

- I have done some changes in the submodule and committed these changes
- Netbenas shows the correct status of the committed files. They are not marked as changed any more. That's correct (so it's different case as in #207067)
- But in Netbenas it is not possible to commit the new version to the main repository to tell the repository to track the new version (see http://stackoverflow.com/a/5542964/1119601)
- In the command line git shows the submodule as "modified ... (new commits)"

It would be really nice if this could be possible in NB.

Thanks so far!

Comment 1 naitsirch 2013-06-21 07:48:53 UTC

Created attachment 136111 [details]
Screenshot of the differences between cmd and Netbeans submodule handling

Comment 2 Ondrej Vrabec 2013-06-21 09:17:45 UTC

it must be fixed as part of bug #207067

*** This bug has been marked as a duplicate of bug 207067 ***