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

Re: Dependency Management

From
Luke Diamand <luke@diamand.org>
Date
Jun 25, 2015, 09:00 UTC
Message-ID
<558BC31B.5000401@diamand.org>
In-Reply-To
<CANuW5x0_B0F-CZ5-iq4c_JiZ99FyUvqywrdA8hPr4Pg2dfZ1sA@mail.gmail.com>
On 23/06/15 19:49, Josh Hagins wrote:
Show 5 quoted lines
> If neither git-submodule nor git-subtree is palatable to you, here are
> a couple of alternatives you might try:
>
>    * https://github.com/ingydotnet/git-subrepo
>    * https://github.com/tdd/git-stree
You could also use Android's "repo" tool:
https://code.google.com/p/git-repo/
Luke
Show 31 quoted lines
>
> On Tue, Jun 23, 2015 at 1:36 PM Stefan Beller <sbeller@google.com> wrote:
>>
>> On Tue, Jun 23, 2015 at 1:52 AM, Jean Audibert <jaudibert@euronext.com> wrote:
>>> Hi,
>>>
>>> Sorry to bother you with this question but I can't find any "official" answer or "strong opinion" from Git community.
>>>
>>> In my company we recently started to use Git and we wonder how to share code and manage dependencies with Git?
>>> Use case: in project P we need to include lib-a and lib-b (libraries shared by several projects)
>>>
>>> In your opinion, what is the "future proof" solution?
>>> * Use submodule
>>> * Use subtree
>>>
>>> We know there is lot of PRO/CONS but I feel that subtree is "behind" in the race and the latest version of submodule work fine
>>
>> Use whatever works fine for your use case.
>>
>> My personal opinion/expectation is to see submodules
>> improving/advancing more than subtrees advancing in the near future.
>> Though this is neither the official nor a strong opinion.
>>
>> Stefan
>>
>>>
>>> Suggestions are very welcome.
>>> Thanks in advance,
>>>
>>> Jean Audibert
>>>
Previous: Josh Hagins
Message 4 of 4 in “Dependency Management”
  1. Jean AudibertJun 23, 2015
  2. Stefan BellerJun 23, 2015
  3. Josh HaginsJun 23, 2015
  4. Luke DiamandJun 25, 2015

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.