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

Re: organizing multiple repositories with dependencies

From
HWHilco Wijbenga <hilco.wijbenga@gmail.com>
Date
Apr 17, 2012, 22:49 UTC
Message-ID
<CAE1pOi2FQtyahcJUJ+CZRLLYN7vxGaOmUiBJ-_AfC-T-ZEY_Sg@mail.gmail.com>
In-Reply-To
<CAJsNXTmfRZvpO=ooB8yKUqGqbU4g5A78=dzt2vPPrs1q+J4ZrA@mail.gmail.com>
On 17 April 2012 15:25, PJ Weisberg <pj@irregularexpressions.net> wrote:
Show 14 quoted lines
> On Tue, Apr 17, 2012 at 2:43 PM, Hilco Wijbenga
> <hilco.wijbenga@gmail.com> wrote:
>
>> I'm assuming that if you have subproject S in umbrella project U and a
>> branch "topic" in U then that same branch should exist in S. Any
>> changes in S's topic should show up in U's topic (probably after some
>> sort of update command like git fetch/pull). This should be unusual,
>> though, you should be working in U, not S. If you want to work on
>> something in S that you don't want to see in U, then you should not be
>> working in S's topic.
>
> This paragraph makes me wonder why you want to use submodules at all.
> Wouldn't a sparse checkout be a better fit for what you're trying to
> accomplish?

No, I don't think so but I could be wrong. I want to be able to easily build and release the individual projects separately (manually and on the build server). I believe that with a sparse checkout I still get the entire directory tree. This just doesn't work well. I can make it work but then I lose other nice features (unrelated to Git).

Basically, I want things separate for release management but together for development.

Previous: PJ WeisbergNext: Namit Bhalla
Message 11 of 34 in “organizing multiple repositories with dependencies”
  1. Namit BhallaApr 16, 2012
  2. Jakub NarebskiApr 16, 2012
  3. dag@cray.comApr 16, 2012
  4. Hilco WijbengaApr 17, 2012
  5. dag@cray.comApr 17, 2012
  6. Seth RobertsonApr 17, 2012
  7. Hilco WijbengaApr 17, 2012
  8. dag@cray.comApr 17, 2012
  9. Hilco WijbengaApr 17, 2012
  10. PJ WeisbergApr 17, 2012
  11. Hilco WijbengaApr 17, 2012
  12. Namit BhallaApr 18, 2012
  13. Jens LehmannApr 18, 2012
  14. dag@cray.comApr 24, 2012
  15. Hilco WijbengaApr 24, 2012
  16. PJ WeisbergApr 24, 2012
  17. Hilco WijbengaApr 24, 2012
  18. dag@cray.comApr 24, 2012
  19. Phil HordApr 30, 2012
  20. dag@cray.comApr 30, 2012
  21. Jens LehmannApr 18, 2012
  22. dag@cray.comApr 24, 2012
  23. Seth RobertsonApr 24, 2012
  24. Jens LehmannApr 24, 2012
  25. Seth RobertsonApr 24, 2012
  26. dag@cray.comApr 24, 2012
  27. username localhostApr 28, 2012
  28. dag@cray.comApr 24, 2012
  29. Seth RobertsonApr 25, 2012
  30. dag@cray.comApr 27, 2012
  31. Eugene SajineApr 24, 2012
  32. Hilco WijbengaApr 24, 2012
  33. dag@cray.comApr 24, 2012
  34. dag@cray.comApr 24, 2012

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.