Git subproject commit Xxxxxxxxxxxxxxxxxxxxx-dirty

-Subproject commit 8c75e65b647238febd0257658b150f717a136359+Subproject commit 8c75e65b647238febd0257658b150f717a136359-dirty

Do not know how to operate the dirty, but the impression of anything has been modified

Workaround, enter the hint in the folder where Git checkout.

Some of the excerpts from the English reply are as follows:

As mentioned in Mark Longair ' s blog post Git Submodules explained,

Versions 1.7.0 and later of git contain an annoying the behavior of git submodule.
Submodules is now regarded as dirty if they has any modified files or untracked files, whereas previously it wo Uld only is the case if HEAD of the submodule pointed to the wrong commit.

The meaning of the plus sign ( + ) in the output of Git submodule have changed, and the first time that you come across T His it takes a little when to figure out what's going wrong, for example by looking through changelogs or using Git bisec T on Git.git to find the change. It would has been much kinder to users to introduce a different symbol for "at the specified version, but dirty".

You can fix it by:

• Either committing or undoing the changes/evolutions within each of your submodules, before going back to the parent repo ( Where the diff shouldn ' t report "dirty" files anymore). To undo all changes to your submodule just into the cd root directory of your submodule git checkout . and do

  Dotnetcarpenter comments that's can do a:git submodule foreach --recursive git checkout .

• Or add --ignore-submodules to your git diff , to temporarily ignore those "dirty" submodules.

New in Git version 1.7.2

As Noam comments below, this question mentions so, since Git version 1.7.2, you can ignore the dirty submodules with:

git status --ignore-submodules=dirty

source of the answer: Http://stackoverflow.com/questions/4873980/git-diff-says-subproject-is-dirty

Git subproject commit Xxxxxxxxxxxxxxxxxxxxx-dirty