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

Re: Composing git repositories

From
Jens Lehmann <jens.lehmann@web.de>
Date
Apr 2, 2013, 19:59 UTC
Message-ID
<515B38B0.2040705@web.de>
In-Reply-To
<CALkWK0nVax9HtM-M2zo-KH6U2jWznaUH9yBn4y1wqDW8f-mfOg@mail.gmail.com>
Am 02.04.2013 20:35, schrieb Ramkumar Ramachandra:
Show 24 quoted lines
> Jens Lehmann wrote:
>> But I think we recently learned to support that use case with
>> submodules. I think there are two floating models:
>>
>> - Tracked:
>> [...]
>>
>> - Untracked:
>>   Some people just want "the newest" tip of a branch checked out in
>>   the submodule and update that from time to time (I suspect this
>>   is because they are used to SVN externals, which I believe work
>>   that way). You throw away reproducibility, which I think is not
>>   good and not the way I expect Git to work.
>> [...]
> 
> Nope, it has nothing to do with SVN externals; I've never used them.
> And no, all repositories aren't created equal.  I should be able to
> add in magit.git into my dotfiles repository without worrying about
> which commits the other repositories were at a particular commit.  If
> my project depends on the bleeding edge of poppler and girarra, I
> should always be able to tell what commits in each subproject the
> build was passing in.  In other words, I should be able to freely
> mixed floating and fixed submodules.  There's no reason for one to be
> Right, and the other to be a shunned second-class citizen.

But you can currently mix floating and fixed submodules, as each submodule can be configured differently. Or am I missing something here?

Previous: Ramkumar RamachandraNext: Jens Lehmann
Message 40 of 43 in “Composing git repositories”
  1. Ramkumar RamachandraMar 26, 2013
  2. Junio C HamanoMar 26, 2013
  3. Ramkumar RamachandraMar 27, 2013
  4. Junio C HamanoMar 27, 2013
  5. Ramkumar RamachandraMar 27, 2013
  6. Junio C HamanoMar 27, 2013
  7. Jonathan NiederMar 27, 2013
  8. Junio C HamanoMar 27, 2013
  9. Jonathan NiederMar 27, 2013
  10. Ramkumar RamachandraMar 28, 2013
  11. Jens LehmannMar 28, 2013
  12. Ramkumar RamachandraMar 28, 2013
  13. Jonathan NiederMar 28, 2013
  14. Jens LehmannMar 28, 2013
  15. Jens LehmannMar 27, 2013
  16. Ramkumar RamachandraMar 28, 2013
  17. Jens LehmannMar 28, 2013
  18. Ramkumar RamachandraMar 31, 2013
  19. Jonathan NiederMar 31, 2013
  20. Ramkumar RamachandraApr 2, 2013
  21. Jeff KingApr 2, 2013
  22. Ramkumar RamachandraApr 2, 2013
  23. Jens LehmannApr 2, 2013
  24. Junio C HamanoApr 2, 2013
  25. Junio C HamanoApr 4, 2013
  26. Duy NguyenApr 5, 2013
  27. Junio C HamanoApr 5, 2013
  28. Duy NguyenApr 5, 2013
  29. Jens LehmannApr 5, 2013
  30. Phil HordMar 31, 2013
  31. Jens LehmannApr 1, 2013
  32. Phil HordApr 1, 2013
  33. Ramkumar RamachandraApr 2, 2013
  34. Jonathan NiederApr 2, 2013
  35. Junio C HamanoApr 2, 2013
  36. Ramkumar RamachandraApr 2, 2013
  37. Jonathan NiederApr 2, 2013
  38. Ramkumar RamachandraApr 2, 2013
  39. Ramkumar RamachandraApr 2, 2013
  40. Jens LehmannApr 2, 2013
  41. Jens LehmannApr 1, 2013
  42. Seth RobertsonApr 1, 2013
  43. Ramkumar RamachandraApr 2, 2013

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.