{"thread":{"id":"38903","subject":"Bug? git push --recurse-submodules=on-demand is not truly recursive","startedAt":"2015-03-24T12:50:13Z","lastAt":"2015-03-24T12:50:13Z","messageCount":1,"participants":["Uwe Sommerlatt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"258406","messageId":"CAGt=MzCkB66K9L6gahUTH3cWafW8psNQYw3d8UKFFy5C+MUZcA@mail.gmail.com","threadId":"38903","inReplyTo":null,"subject":"Bug? git push --recurse-submodules=on-demand is not truly recursive","fromName":"Uwe Sommerlatt","fromEmail":"uwe.sommerlatt@gmail.com","sentAt":"2015-03-24T12:50:13Z","receivedAt":"2015-03-24T12:50:13Z","isPatch":false,"sender":{"key":"uwe.sommerlatt@gmail.com","avatar":null},"body":"I have the following project structure:\n\nroot-project\n      |\n      |-- A\n      |   |\n      |   |-- C\n      |\n      |-- B\n\nA and B are submodules of the root-project. C is in turn a submodule\nof project A. Suppose I have made changes to projects A,B and C and\ncommited these changes to the respective indices. After that I update\nthe references to A and B in the root-project and commit that change\nas well. When I push the commit of the root-project with the option\n--recurse-submodules=on-demand, git pushes the commits of projects A,\nB and the root-project but silently ignores all unpublished commits of\nproject C. I end up publishing a project that no one can successfully\nclone because of the dangling link to C. Is this the expected\nbehaviour or is this a bug?\n\nI have written a small shell script that sets up the project structure\nand executes the described scenario:\nhttps://gist.github.com/usommerl/6e8defcba94bd4ba1438\n\ngit version 2.3.3\n\nUwe Sommerlatt\n"}]}