git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git support for subprojects?
Date: Wed, 14 Mar 2007 02:11:51 +0100	[thread overview]
Message-ID: <et7hvh$phh$1@sea.gmane.org> (raw)
In-Reply-To: OFD596829F.8C32CA61-ON8625729D.004F66DC-8625729D.00501D41@BJSERVICES.COM

[Cc: git@vger.kernel.org]

Luke.Powell@bjservices.com wrote:

> Say that I have projects A and B which both depend on another project Z. 
> Whenever I update one of those projects, I'd like to also update to the 
> latest version of Z in a subdirectory. Is there that kind of support for 
> these subprojects? If I'm not being clear, I'm talking about the kind of 
> support that is available in Subversion through svn:externals or something 
> analogous.

Git currently doesn't have submodule (subproject) support, although this
topic appears from time to time on git mailing list. There are even two
prototypes of proper submodule support; link to one of those (heavyweight
one by Martin Waitz) can be found at
  http://git.or.cz/gitwiki/SubprojectSupport
There is also lightweight submodule support proposal, but as author did
not put info in above page, and I don't have I think an URL saved...
It is I think what you might want.

But it should be fairly easy to cobble together something analogous
to broken[*1*] svn:externals with update hook...
 
> Also, please cc me in any answers since I'm not sure my subscription to 
> the list went through.

http://git.or.cz/gitwiki/GitCommunity  


[*1*] In short: you really, really want to bind/connect submodule commit
(submodule version) to supermodule (main module) commit. E.g. you want to
know for sure that v2.1.3 of your project pass all the tests and works
with v0.2.1 of a submodule.
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

      parent reply	other threads:[~2007-03-14  1:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-13 14:32 git support for subprojects? Luke.Powell
2007-03-13 15:51 ` Shawn O. Pearce
2007-03-14  1:11 ` Jakub Narebski [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

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

  git send-email \
    --in-reply-to='et7hvh$phh$1@sea.gmane.org' \
    --to=jnareb@gmail.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.
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 NNTP newsgroup(s).