{"thread":{"id":"51101","subject":"Setting submodule.recurse true can lead to loose of changes","startedAt":"2019-05-15T14:02:30Z","lastAt":"2019-05-15T14:02:30Z","messageCount":1,"participants":["Stefan Sonski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"375629","messageId":"CAGR_whtu75fcWGz-EALyXLTWkPCu-rHK8r0M7Lr2t71RKT-kww@mail.gmail.com","threadId":"51101","inReplyTo":null,"subject":"Setting submodule.recurse true can lead to loose of changes","fromName":"Stefan Sonski","fromEmail":"s.sonski@gmail.com","sentAt":"2019-05-15T14:02:17Z","receivedAt":"2019-05-15T14:02:30Z","isPatch":false,"sender":{"key":"s.sonski@gmail.com","avatar":null},"body":"Hi all,\n\nI discovered a potential bug regarding submodules and the use of\nrebase and stash.\n\nWhen setting the configuration submodule.recurse true, doing changes\nin the super project and also given submodule, these changes are lost,\nwhen doing a rebase or stash. The stash even shows these changes with\nstash show -p, but trying to apply them, leads also to a lost of these\nchanges.\n\nRemoving submodule.recurse and setting fetch.recurseSubmodules and\npush.recurseSubmodules fixes this problem, because the submodule is\nnot touched.\n\nStefan\n"}]}