{"push_id":1254965076,"size":1,"distinct_size":0,"ref":"refs/heads/sb/submodule-clone-rr","head":"a192c397f449ec59734d01a85a4d540bf338787f","before":"5dded239d2cc5132bbc2e7959e6066329ae90f5d","commits":[{"sha":"a192c397f449ec59734d01a85a4d540bf338787f","author":{"name":"Stefan Beller","email":"75e5af3a5fc6e432c184f339c5c73c118a246be6@google.com"},"message":"clone: recursive and reference option triggers submodule alternates\n\nWhen `--recursive` and `--reference` is given, it is reasonable to\nexpect that the submodules are created with references to the submodules\nof the given alternate for the superproject.\n\n  An initial attempt to do this was presented to the mailing list, which\n  used flags that are passed around (\"--super-reference\") that instructed\n  the submodule clone to look for a reference in the submodules of the\n  referenced superproject. This is not well thought out, as any further\n  `submodule update` should also respect the initial setup.\n\n  When a new  submodule is added to the superproject and the alternate\n  of the superproject does not know about that submodule yet, we rather\n  error out informing the user instead of being unclear if we did or did\n  not use a submodules alternate.\n\nTo solve this problem introduce new options that store the configuration\nfor what the user wanted originally.\n\nSigned-off-by: Stefan Beller <sbeller@google.com>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/gitster/git/commits/a192c397f449ec59734d01a85a4d540bf338787f"}]}
{"actor":{"display_login":"gitster"}}