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

git submodule update needs to be at the toplevel of working tree, why?

From
OOOdin Hørthe Omdal <odinho@opera.com>
Date
Nov 22, 2013, 13:22 UTC
Message-ID
<1385126550.10973.50760825.6B70B959@webmail.messagingengine.com>
Hi,

I'm usually in a subfolder doing actual work. A very common problem I have is wanting to do a submodule update, but git really hates that. And I wonder why?

It wouldn't be hard to cd to the toplevel working directory, do the update, and cd back. It's what I have to do manually every time now already:

  $ git submodule update
  You need to run this command from the toplevel of the working tree.
  $ cd ../..
  $ git submodule update
  Submodule path 'myproject/libs/external-module': checked out
  '434fdf32a7add62...
  $ cd -

I see that it comes from git-sh-setup, so no rationale for this rather weird and surprising behavior is given in the git-submodule file. :)

-- 
  Odin Hørthe Omdal
  odinho@opera.com
Next: John Keeping
Message 1 of 3 in “git submodule update needs to be at the toplevel of working tree, why?”
  1. Odin Hørthe OmdalNov 22, 2013
  2. John KeepingNov 22, 2013
  3. Odin Hørthe OmdalNov 22, 2013

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.