git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jean Audibert <jaudibert@euronext.com>
To: "'git@vger.kernel.org'" <git@vger.kernel.org>
Subject: Dependency Management
Date: Tue, 23 Jun 2015 08:52:16 +0000	[thread overview]
Message-ID: <45DF444C03B59343B5893402DC4F867E3A800EF8@PB2OAEXM01.oad.exch.int> (raw)
In-Reply-To: <45DF444C03B59343B5893402DC4F867E3A800EC7@PB2OAEXM01.oad.exch.int>

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

Suggestions are very welcome.
Thanks in advance,

Jean Audibert


_________________________________________________________________

This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of Euronext N.V. or any of its subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired.

       reply	other threads:[~2015-06-23  8:52 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 ` Jean Audibert [this message]
2015-06-23 17:34   ` Dependency Management Stefan Beller
2015-06-23 18:49     ` Josh Hagins
2015-06-25  9:00       ` Luke Diamand

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=45DF444C03B59343B5893402DC4F867E3A800EF8@PB2OAEXM01.oad.exch.int \
    --to=jaudibert@euronext.com \
    --cc=git@vger.kernel.org \
    /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).