象牙齿类子类的地位报告方式在最近版本的 g类中发生了很大变化,因此,你应当真正包括<条码>(git)——转录<<>/代码”的产出,并且使我们能够准确地提供帮助。
但无论如何,<代码>git diff example.com/deptmanager的产出 应该告诉大家。 如果你以相同名称看到产出,但以<代码>-dirty 加入新版本,例如:
diff --git a/example.com/soundmanager b/example.com/soundmanager
--- a/example.com/soundmanager
+++ b/example.com/soundmanager
@@ -1 +1 @@
-Subproject commit c5c6bbaf616d64fbd873df7b7feecebb81b5aee7
+Subproject commit c5c6bbaf616d64fbd873df7b7feecebb81b5aee7-dirty
... than that means that git status
in the submodule isn t clean - try cd example.com/soundmanager
and then git status
to see what s going on.
On the other hand, if you see different commit versions, e.g.:
diff --git a/example.com/soundmanager b/example.com/soundmanager
index c4478af..c79d9c8 160000
--- a/example.com/soundmanager
+++ b/example.com/soundmanager
@@ -1 +1 @@
-Subproject commit c4478af032e604bed605e82d04a248d75fa513f7
+Subproject commit c79d9c83c2864665ca3fd0b11e20a53716d0cbb0
... that means that the version that your submodule is at (i.e. what you see from cd example.com/soundmanager && git show HEAD
) is different from the version committed in the main project s tree (i.e. what you see from git rev-parse HEAD:example.com/soundmanager
). If the former is right, you should add and commit the new version of the submodule in your main project, with something like:
git add example.com/soundmanager
git commit -m "Update the soundmanager submodule"
另一方面,如果后者是你想要的,你就可以改变该分单元的版本:
git submodule update example.com/soundmanager