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

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

From
John Keeping <john@keeping.me.uk>
Date
Nov 22, 2013, 13:47 UTC
Message-ID
<20131122134747.GC15033@serenity.lan>
In-Reply-To
<1385126550.10973.50760825.6B70B959@webmail.messagingengine.com>
On Fri, Nov 22, 2013 at 02:22:30PM +0100, Odin Hørthe Omdal wrote:
Show 7 quoted lines
> 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:
This restriction was removed in Git 1.8.4.
Previous: Odin Hørthe OmdalNext: Odin Hørthe Omdal
Message 2 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.