{"thread":{"id":"10389","subject":"Issues for git-submodule","startedAt":"2007-10-20T07:31:00Z","lastAt":"2007-10-20T07:31:00Z","messageCount":1,"participants":["Yin Ping"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"56674","messageId":"46dff0320710200031x2a58706cl7d3df11cad12d4d2@mail.gmail.com","threadId":"10389","inReplyTo":"46dff0320710200027o5fe434b4i9bd4f3ffc17f03f6@mail.gmail.com","subject":"Issues for git-submodule","fromName":"Yin Ping","fromEmail":"pkufranky@gmail.com","sentAt":"2007-10-20T07:31:00Z","receivedAt":"2007-10-20T07:31:00Z","isPatch":false,"sender":{"key":"pkufranky@gmail.com","avatar":"https://avatars.githubusercontent.com/u/5346?v=4"},"body":"1. gti-submodule status\n   As the manual says, '+'  is shown if the currently checked out\nsubmodule commit does not match the SHA-1 found in the index of the\ncontaining repository.\n\n  However, not matching has two cases: one is a new commit in the\nsubmodule, the other  is update of index of the submodule after a\ncommand such as \"git-pull\".\n\n  So which is the case when a '+' is seen? Should i run 'git-commit'\nor 'git-submodule update'? As a suggestion, I think git should tell\nthe user which commit  is newer (the one in supermodule index or the\nHEAD of the submodule) and even give the log entry between the two\ncommits.\n\n2. As I first saw 'git-submodule status submoduepath',  I thought it\nshould do the following thing\n   cd submoduepath && git-status && cd -\n\n   This is actually what i need, espacially when i have a lot of\nsubmodules and has made changes in some modules. How do i know which\nmodules have been changed and how they have been changed?\n\n  So, In some degree, I even think current 'git-submodule status'\nshould be replaced by git-status and the right thing 'git-submodule\nstatus' should do is to show the status of submodule itself as i just\nsaid above.\n\n\n--\nfranky\n"}]}