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

Problem with --shallow-submodules option

From
IZIstvan Zakar <istvan.zakar@gmail.com>
Date
Jun 20, 2016, 13:06 UTC
Message-ID
<loom.20160620T145755-931@post.gmane.org>
Hello,

I'm working on a relatively big project with many submodules. During cloning for testing I tried to decrease the amount of data need to be fetched from the server by using --shallow-submodules option in the clone command. It seems to check out the tip of the remote repo, and if it's not the commit registered in the superproject the submodule update fails (obviously). Can I somehow tell to fetch that exact commit I need for my superproject?

Thanks,
   Istvan
Next: Stefan Beller
Message 1 of 8 in “Problem with --shallow-submodules option”
  1. Istvan ZakarJun 20, 2016
  2. Stefan BellerJun 20, 2016
  3. Istvan ZakarJun 21, 2016
  4. Stefan BellerJun 21, 2016
  5. Fredrik GustafssonJun 22, 2016
  6. Istvan ZakarJun 30, 2016
  7. Stefan BellerJun 30, 2016
  8. Istvan ZakarJun 30, 2016

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.