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

Re: Subprojects tasks

From
JWJosef Weidendorfer <josef.weidendorfer@gmx.de>
Date
Dec 17, 2006, 00:32 UTC
Message-ID
<200612170132.14276.Josef.Weidendorfer@gmx.de>
In-Reply-To
<20061216225810.GD12411@admingilde.org>
On Saturday 16 December 2006 23:58, Martin Waitz wrote:
Show 8 quoted lines
> > If the plumbing layer does not have to (although I haven't
> > thought it through, it does feel like it even shouldn't) unwrap
> > "link" and let the Porcelain layer to deal with it, that would
> > certainly make rev-list/revision.c part simpler.
> 
> Yes.  However, it makes other things more complicated.
> If the plumbing does not do all the subproject stuff and you don't have
> everything in one database

Even without plumbing doing the subproject stuff, we could use the same, unified database for the objects. Or do I miss something?

As you said: the problem are submodule commit in superproject trees which are not reachable by refs of the submodule. However, we only need these commits when cloning/fetching the submodule in the scope of cloning/fetching the superproject; we simply can not use here a normal repository of the submodule, as these commits would be not available there.

We should add a plumbing command for "Give me the minimal set of commits (from all submodules) which have all the submodule link object ids as ancestors which appear in the history of a given commit (from a superproject)". With this, building the set of objects to pack/fetch/clone into a unified object database for a superproject with its submodules should be easy.

It is also needed for pruning the unified object database. Pruning in submodules simply would print out an error "Pruning in submodules not supported. Prune in the superproject instead".

Josef
Previous: Sven VerdoolaegeNext: Alan Chandler
Message 21 of 24 in “Subprojects tasks”
  1. Junio C HamanoDec 16, 2006
  2. Jakub NarebskiDec 16, 2006
  3. Martin WaitzDec 16, 2006
  4. Jakub NarebskiDec 16, 2006
  5. Josef WeidendorferDec 17, 2006
  6. Martin WaitzDec 17, 2006
  7. Jakub NarebskiDec 17, 2006
  8. Martin WaitzDec 17, 2006
  9. Jakub NarebskiDec 17, 2006
  10. Martin WaitzDec 17, 2006
  11. Josef WeidendorferDec 17, 2006
  12. Martin WaitzDec 18, 2006
  13. Josef WeidendorferDec 17, 2006
  14. Martin WaitzDec 18, 2006
  15. Josef WeidendorferDec 18, 2006
  16. Josef WeidendorferDec 17, 2006
  17. Sven VerdoolaegeDec 16, 2006
  18. Junio C HamanoDec 16, 2006
  19. Martin WaitzDec 16, 2006
  20. Sven VerdoolaegeDec 16, 2006
  21. Josef WeidendorferDec 17, 2006
  22. Alan ChandlerDec 17, 2006
  23. Jakub NarebskiDec 17, 2006
  24. Martin WaitzDec 17, 2006

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.