Issues for git-submodule

Issues for git-submodule

[Yin Ping]

1. gti-submodule status
   As the manual says, '+'  is shown if the currently checked out
submodule commit does not match the SHA-1 found in the index of the
containing repository.

  However, not matching has two cases: one is a new commit in the
submodule, the other  is update of index of the submodule after a
command such as "git-pull".

  So which is the case when a '+' is seen? Should i run 'git-commit'
or 'git-submodule update'? As a suggestion, I think git should tell
the user which commit  is newer (the one in supermodule index or the
HEAD of the submodule) and even give the log entry between the two
commits.

2. As I first saw 'git-submodule status submoduepath',  I thought it
should do the following thing
   cd submoduepath && git-status && cd -

   This is actually what i need, espacially when i have a lot of
submodules and has made changes in some modules. How do i know which
modules have been changed and how they have been changed?

  So, In some degree, I even think current 'git-submodule status'
should be replaced by git-status and the right thing 'git-submodule
status' should do is to show the status of submodule itself as i just
said above.


--
franky