On Sun, Oct 28, 2012 at 1:02 AM, Jens Lehmann <Jens.Lehmann@xxxxxx> wrote: > Am 26.10.2012 22:43, schrieb Francis Moreau: >> On Fri, Oct 26, 2012 at 10:05 PM, Jens Lehmann <Jens.Lehmann@xxxxxx> wrote: >> [...] >>> >>> That is weird, "git diff --submodule" should show that too. Is there >>> anything unusual about your setup? (The only explanation I can come >>> up with after checking the code is that your submodule has neither a >>> .git directory nor a gitfile or the objects directory in there doesn't >>> contain these commits) >> >> Oh now you're asking, I think the submodule has been added by using >> the --reference option of git-submodule-add. >> >> $ cd configs >> $ cat .git >> gitdir: ../.git/modules/configs > > Thanks, I suspect the --reference option makes the difference here, > I'll check that as soon as I find some time. Yes that's fairly easy to reproduce: $ mkdir super $ cd super $ git init $ git submodule add --reference ~/tmp/git-submodule/public/a.git ~/tmp/git-submodule/public/a.git a $ git commit -m "Initial creation of super project" $ cd a $ date >a.txt $ git commit -a -m "add to a.txt a random change" $ cd .. $ git submodule summary * a 2f8803a...a1aa4bf (1): > add to a.txt a random change $ git commit -a -m "Include a's changes in super project" $ git diff --submodule=log HEAD~1 HEAD Submodule a 2f8803a...a1aa4bf (commits not present) Thanks -- Francis -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html