Hello, Sorry again for the mailing list...
On Thu, Oct 6, 2016 at 11:20 AM, Heiko Voigt <hvo...@hvoigt.net> wrote: > So I guess the same applies to 'git status'? No, it is the strange thing. As told in my very first message here what happens after git diff and git status: $ git clone https://github.com/githubtraining/example-dependency.git Cloning into 'example-dependency'... remote: Counting objects: 35, done. remote: Total 35 (delta 0), reused 0 (delta 0), pack-reused 35 Unpacking objects: 100% (35/35), done. Checking connectivity... done. $ cd example-dependency $ git submodule deinit js fatal: Please stage your changes to .gitmodules or stash them to proceed Submodule work tree 'js' contains local modifications; use '-f' to discard them $ git diff [no output] $ git submodule deinit js fatal: Please stage your changes to .gitmodules or stash them to proceed Submodule work tree 'js' contains local modifications; use '-f' to discard them $ git status On branch master Your branch is up-to-date with 'origin/master'. nothing to commit, working directory clean $ git submodule deinit js Cleared directory 'js' So as you can see, the 'git status' makes the problem magically disappear. Thomas
