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

Submodule idea

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Sep 29, 2007, 19:04 UTC
Message-ID
<Pine.LNX.4.64.0709291442430.5926@iabervon.org>

I *think* that it would be a great benefit if "git submodule update" would leave you on a branch if (a) you were on that branch before, and (b) pulling on that branch would update it to the commit that the superproject specifies for that submodule.

Or maybe there should be a "git submodule fetch" which fetches from the remote, and replaces FETCH_HEAD with the superproject's index entry, and "git submodule pull" would merge it? (With the model being that the entry in the superproject is an additional remote that you both track and publish to)

	-Daniel
*This .sig left intentionally blank*
Message 1 of 1 in “Submodule idea”
  1. Daniel BarkalowSep 29, 2007

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.