git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Setting submodule.recurse true can lead to loose of changes

From
SSStefan Sonski <s.sonski@gmail.com>
Date
May 15, 2019, 14:02 UTC
Message-ID
<CAGR_whtu75fcWGz-EALyXLTWkPCu-rHK8r0M7Lr2t71RKT-kww@mail.gmail.com>
Hi all,

I discovered a potential bug regarding submodules and the use of rebase and stash.

When setting the configuration submodule.recurse true, doing changes in the super project and also given submodule, these changes are lost, when doing a rebase or stash. The stash even shows these changes with stash show -p, but trying to apply them, leads also to a lost of these changes.

Removing submodule.recurse and setting fetch.recurseSubmodules and push.recurseSubmodules fixes this problem, because the submodule is not touched.

Stefan
Message 1 of 1 in “Setting submodule.recurse true can lead to loose of changes”
  1. Stefan SonskiMay 15, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.