From: Luke Diamand <luke@diamand.org>
To: Josh Hagins <hagins.josh@gmail.com>,
Stefan Beller <sbeller@google.com>,
Jean Audibert <jaudibert@euronext.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Dependency Management
Date: Thu, 25 Jun 2015 10:00:11 +0100 [thread overview]
Message-ID: <558BC31B.5000401@diamand.org> (raw)
In-Reply-To: <CANuW5x0_B0F-CZ5-iq4c_JiZ99FyUvqywrdA8hPr4Pg2dfZ1sA@mail.gmail.com>
On 23/06/15 19:49, Josh Hagins wrote:
> 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
>
> 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
>>>
prev parent reply other threads:[~2015-06-25 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45DF444C03B59343B5893402DC4F867E3A800EC7@PB2OAEXM01.oad.exch.int>
2015-06-23 8:52 ` Dependency Management Jean Audibert
2015-06-23 17:34 ` Stefan Beller
2015-06-23 18:49 ` Josh Hagins
2015-06-25 9:00 ` Luke Diamand [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=558BC31B.5000401@diamand.org \
--to=luke@diamand.org \
--cc=git@vger.kernel.org \
--cc=hagins.josh@gmail.com \
--cc=jaudibert@euronext.com \
--cc=sbeller@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).