Re: Notes on Using Git with Subprojects
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Sep 27, 2006, 23:14 UTC
- Message-ID
- <Pine.LNX.4.63.0609280113490.14200@wbgn013.biozentrum.uni-wuerzburg.de>
- In-Reply-To
- <451AB122.9020600@gmail.com>
Hi,
On Wed, 27 Sep 2006, A Large Angry SCM wrote:
Show 23 quoted lines
> Johannes Schindelin wrote: > > Hi, > > > > On Wed, 27 Sep 2006, Martin Waitz wrote: > > > > > On Tue, Sep 26, 2006 at 03:33:49PM -0700, A Large Angry SCM wrote: > > > > So, for each subproject of a parent project, you want to record branch, > > > > version (commit ID), and directory location. Not quite as easy to do in > > > > a makefile but do-able. > > > I've been playing with this kind of subprojects a little bit. > > > > > > My current approach is like this: > > > > > > * create a .gitmodules file which lists all the directories > > > which contain a submodule. > > > * the .git/refs/heads directory of the submodule gets stored in > > > .gitmodule/<modulename> inside the parent project > > > > Taking this a step further, you could make subproject/.git/refs/heads a > > symbolic link to .git/refs/heads/subproject, with the benefit that fsck Just > > Works. > > Wouldn't an fsck in the parent complain about missing objects?
... not if my original idea (which I might have forgotten to mention ;-) was implemented: symlinking subproject/.git/objects to .git/objects.
Ciao, Dscho