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

Re: Making submodules easier to work with

From
RSRoman Shaposhnik <rvs@sun.com>
Date
May 6, 2008, 23:17 UTC
Message-ID
<1210115872.25663.1097.camel@work.sfbay.sun.com>
In-Reply-To
<3B9C16C0-0D0C-42D3-8315-72C8D8C88452@midwinter.com>
On Thu, 2008-05-01 at 16:29 -0700, Steven Grimm wrote:
Show 8 quoted lines
> On May 1, 2008, at 11:38 AM, Finn Arne Gangstad wrote:
> > Where do we want to go with submodules?
> 
> I have two uses for submodules.
> 
> The first one is... well, not really submodules at all. I really want  
> sparse checkout so I can avoid bothering with parts of the larger  
> project tree I don't care about or need.

When you say "checkout" do you really mean "git checkout" (IOW, you still have the history for *everything* in .git but you just don't want your working tree to be polluted by the stuff you don't need at the moment) or are you talking about "partial cloning"? The reason I'm asking is because a need for "partial cloning" is very real around where I work. Which is easy to understand because TeamWare (a precursor to BitKeeper) supports such a concept. Now, before I get beaten to death: I DO understand why "partial cloning" and changeset-oriented SCMs don't go together well. Yet, it seems to me that a sort of "transitive closure" of the changesets for the files I'm actually interested in might be a natural way of having such a feature.

>  But right now submodules are  
> the only way to approximate sparse checkout,

For us submodules seem to be the only way to approximate "sparse cloning" and that's why the usage patterns I worry about don't necessarily match the ones that drive "git submodule"

Thanks, Roman.

Previous: Steven GrimmNext: Ping Yin
Message 21 of 22 in “Making submodules easier to work with (auto-update on checkout or merge, stash & restore submodules)”
  1. Tim HarperApr 30, 2008
  2. Tim HarperApr 30, 2008
  3. Andreas EricssonApr 30, 2008
  4. Johannes SchindelinApr 30, 2008
  5. Avery PennarunApr 30, 2008
  6. Ping YinApr 30, 2008
  7. Roman ShaposhnikApr 30, 2008
  8. Avery PennarunApr 30, 2008
  9. Tim HarperApr 30, 2008
  10. Avery PennarunApr 30, 2008
  11. Tim HarperApr 30, 2008
  12. Avery PennarunApr 30, 2008
  13. Roman ShaposhnikApr 30, 2008
  14. Avery PennarunApr 30, 2008
  15. Finn Arne GangstadMay 1, 2008
  16. Avery PennarunMay 1, 2008
  17. Roman ShaposhnikMay 6, 2008
  18. Avery PennarunMay 7, 2008
  19. Ping YinMay 8, 2008
  20. Steven GrimmMay 1, 2008
  21. Roman ShaposhnikMay 6, 2008
  22. Ping YinMay 1, 2008

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.