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

Re: Notes on Using Git with Subprojects

From
A Large Angry SCM <gitzilla@gmail.com>
Date
Sep 26, 2006, 22:45 UTC
Message-ID
<4519AD9F.7020303@gmail.com>
In-Reply-To
<Pine.LNX.4.63.0609270009400.25371@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
Show 19 quoted lines
> Hi,
> 
> On Tue, 26 Sep 2006, A Large Angry SCM wrote:
> 
>> How the state (subproject list, branch names, etc.) is recorded in a 
>> parent project is only important to the parent project. The parent 
>> project must also know how to interact with with each of its 
>> subprojects.
> 
> Granted, if you mix VCSes, this is most pragmatic.
> 
> But it is also wrong: The whole point in bundling the subprojects together 
> is (IMHO) to get the benefits of a VCS for the root project, i.e. for the 
> combined states of the subprojects. After all, you want to say "I know 
> that this collection of projects at these states compiled and worked 
> fine."
> 
> And if you let a build system handle the stitching of the subprojects, you 
> completely lose these benefits.

Bundling and subproject support are two different things. Bundling is for convenience. Subprojects are usually the result of a dependency on a project managed or controlled by some other entity or on some part of the larger project with radically different development requirements.

Recording which version of a subproject to use is important and my note failed to discuss it. That I'll remedy over the next several days.

Previous: Johannes SchindelinNext: Daniel Barkalow
Message 5 of 39 in “Notes on Using Git with Subprojects”
  1. A Large Angry SCMSep 26, 2006
  2. Johannes SchindelinSep 26, 2006
  3. A Large Angry SCMSep 26, 2006
  4. Johannes SchindelinSep 26, 2006
  5. A Large Angry SCMSep 26, 2006
  6. Daniel BarkalowSep 26, 2006
  7. Shawn PearceSep 26, 2006
  8. A Large Angry SCMSep 26, 2006
  9. Martin WaitzSep 27, 2006
  10. Johannes SchindelinSep 27, 2006
  11. Martin WaitzSep 27, 2006
  12. Johannes SchindelinSep 27, 2006
  13. Sven VerdoolaegeSep 27, 2006
  14. Junio C HamanoSep 27, 2006
  15. Michael S. TsirkinSep 28, 2006
  16. Jeff KingSep 28, 2006
  17. Martin WaitzSep 27, 2006
  18. Johannes SchindelinSep 27, 2006
  19. A Large Angry SCMSep 27, 2006
  20. Johannes SchindelinSep 27, 2006
  21. Shawn PearceSep 27, 2006
  22. Rogan DawesSep 27, 2006
  23. Shawn PearceSep 28, 2006
  24. A Large Angry SCMSep 28, 2006
  25. A Large Angry SCMSep 28, 2006
  26. A Large Angry SCMSep 27, 2006
  27. Jeff KingSep 27, 2006
  28. A Large Angry SCMSep 28, 2006
  29. Jeff KingSep 28, 2006
  30. Shawn PearceSep 28, 2006
  31. Jeff KingSep 28, 2006
  32. Shawn PearceSep 28, 2006
  33. Shawn PearceSep 28, 2006
  34. Johannes SchindelinSep 28, 2006
  35. Martin WaitzSep 28, 2006
  36. A Large Angry SCMSep 28, 2006
  37. Martin WaitzSep 29, 2006
  38. A Large Angry SCMSep 26, 2006
  39. A Large Angry SCMOct 1, 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.