Commit dialog fails to warn submodule dirty state
By @ch3cooli on December 01, 2012 13:11 (imported from Google Code)
This reflects a regression of Issue #1472 (closed) (commit message only),
as well as a bug in Issue #1411 (closed) (warn dirty submodule on commit).
What steps will reproduce the problem?
Case 1: Existing submodule
- Make an existing submodule dirty
- Commit the superproject using Commit Dialog
After fixing the problem for case 1, the problem for case 2 is unhidden
Case 2: New submodule
- Add a submodule
- Change a tracked file in the superproject
- Commit the superproject using Commit Dialog
What is the expected output? What do you see instead?
Case 1:
Expected: Warn that the submodule is dirty and ask the user if he wants to commit submodule.
Actual: No warning. The superproject is committed.
Case 2:
Expected: No warning. The superproject is committed.
Actual: Warn that submodule is dirty.
What version of TortoiseGit and msysgit are you using? On
what operating system?
TortoiseGit 1.7.15