All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Namit Bhalla <namitbhalla@yahoo.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: organizing multiple repositories with dependencies
Date: Mon, 16 Apr 2012 07:30:17 -0700 (PDT)	[thread overview]
Message-ID: <m3hawjagw9.fsf@localhost.localdomain> (raw)
In-Reply-To: <1334568432.53977.YahooMailNeo@web65906.mail.ac4.yahoo.com>

Namit Bhalla <namitbhalla@yahoo.com> writes:

> I am looking to track some projects using Git with each project as a 
> separate repository.
> Even after reading the documentation, I am still wondering if there is a 
> way to organize things as described below.
> 
> Consider 2 projects, Project-a and Project-b, which are housed in 
> repositories Repo-a and Repo-b respectively. 
> Project-a develops reusable libraries which are needed by Project-b 
> (otherwise Project-b will not compile).
> When a new stable version of Project-a libraries has to be delivered, they 
> are "checked into" a path in Repo-a.
> Now, I would like to setup Repo-b so that when someone starts working on 
> Project-b, he should be able to retrieve the code from Repo-b as well as the libraries from Repo-a. Is there any way to achieve that in 
> Git?

Put reusable library in its own repository, and use submodules to link
it up to project-a and project-b repositories.

HTH
-- 
Jakub Narebski

  reply	other threads:[~2012-04-16 14:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16  9:27 organizing multiple repositories with dependencies Namit Bhalla
2012-04-16 14:30 ` Jakub Narebski [this message]
2012-04-16 20:08   ` dag
2012-04-17 17:29     ` Hilco Wijbenga
2012-04-17 17:51       ` dag
2012-04-17 18:37       ` Seth Robertson
2012-04-17 19:55         ` Hilco Wijbenga
2012-04-17 20:51           ` dag
2012-04-17 21:43             ` Hilco Wijbenga
2012-04-17 22:25               ` PJ Weisberg
2012-04-17 22:49                 ` Hilco Wijbenga
2012-04-18 10:15                   ` Namit Bhalla
2012-04-18 12:09               ` Jens Lehmann
2012-04-24 17:17               ` dag
2012-04-24 18:54                 ` Hilco Wijbenga
2012-04-24 21:09                   ` PJ Weisberg
2012-04-24 22:04                     ` Hilco Wijbenga
2012-04-24 23:33                   ` dag
2012-04-30 19:25                     ` Phil Hord
2012-04-30 19:43                       ` dag
2012-04-18 12:19             ` Jens Lehmann
2012-04-24 17:22               ` dag
2012-04-24 17:59                 ` Seth Robertson
2012-04-24 20:26                   ` Jens Lehmann
2012-04-24 20:52                     ` Seth Robertson
2012-04-24 23:21                     ` dag
2012-04-28 17:31                       ` username localhost
2012-04-24 23:25                   ` dag
2012-04-25 12:48                     ` Seth Robertson
2012-04-27 14:23                       ` dag
2012-04-24 19:48 ` Eugene Sajine
2012-04-24 22:11   ` Hilco Wijbenga
2012-04-24 23:38     ` dag
2012-04-24 23:36   ` dag

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3hawjagw9.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=namitbhalla@yahoo.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.