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

Re: Composing git repositories

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 5, 2013, 04:53 UTC
Message-ID
<7vwqshefyk.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CACsJy8C_dRqdPvAUW19zVLrJQGqFCRu_TaPMnRbkfgq+H9V2dw@mail.gmail.com>
Duy Nguyen <pclouds@gmail.com> writes:
> Should someone add these links to the source code (maybe as a comment
> in submodule.c, or above the definition of S_IFGITLINK in cache.h)?

They were given in response to a request for reading material to learn background. Most of the straw-man outlines raised in these old discussoin threads are very different from what we ended up doing, and their value is mostly to learn what kind of use cases should one consider if one were designing subproject support from scratch, what possible approaches were considered and what were found already lacking in them before we even had a working prototype (in other words, to learn where one should _not_ go).

Link themselves are not very useful and definitely not appropriate as a comment next to S_IFGITLINK, as S_IFGITLINK is not the only thing that implements the subproject support, and not all the ideals dreamed in these threads are realized with the implementation (yet).

> A brief summary or outcome from these links in the comment would
> be nice.

A summary of what to consider in Documentation/technical/ somewhere may be a very welcome addition. Thanks for volunteering ;-).

Previous: Duy NguyenNext: Duy Nguyen
Message 27 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.