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

[RFC] What to you think about a loose status for submodules?

From
Heiko Voigt <hvoigt@hvoigt.net>
Date
Oct 21, 2009, 16:01 UTC
Message-ID
<20091021160122.GA2067@book.hvoigt.net>
Hi,

for some time now I have been thinking about submodules which are not checked out by default. So for example if you have a project which consist of the submodules:

project/core
       /help
       /app
...

Consider the situation that 'help' is really big because it is a user friendly application ;)

So you usually do not need the help folder to develop the application but it still is tied to a certain revision.

For such a workflow I would like to implement what I call 'loose' submodules. Where a

  git clone project.git
  cd project
  git submodule init && git submodule update
would omit the 'help' folder. But in case I specify it directly like
  git submodule init help
it would update to the recorded revision.
Of course the relation would be configurable. E.g.:
  git config submodule."name".relation loose
and the opposite as
  git config submodule."name".relation tight

Initially the implementation would only deal with the initialization case. As a second step I would like to deal with the situation whether a submodule should be shown as changed or not. What do you think about such an extension?

cheers Heiko
Next: Junio C Hamano
Message 1 of 6 in “[RFC] What to you think about a loose status for submodules?”
  1. Heiko VoigtOct 21, 2009
  2. Junio C HamanoOct 21, 2009
  3. Heiko VoigtOct 22, 2009
  4. Junio C HamanoOct 22, 2009
  5. Heiko VoigtJan 20, 2010
  6. Junio C HamanoJan 20, 2010

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.