RE: Mixing and matching multiple projects

From

HLHolding, Lawrence <lawrence.holding@cubic.com>

Date

Feb 20, 2012, 00:17 UTC

Message-ID

<A5E8E180685CEF45AB9E737A010799802D972E@cdnz-ex1.corp.cubic.cub>

In-Reply-To

<7v39a9tf45.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

> Junio C Hamano <gitster@pobox.com> writes:
> 
> > But I wonder if we can do without forking the /s/xyzzy/os/.git

submodule?

> >
> > If we *could* do this:
> >
> > 	cd /s/xyzzy
> >       mkdir os/drivers/frotz && populate the directory with sources
> 
> A crucial step was missing here for my story to make *any* sense.

Sorry.

> A step to create a repository at /s/xyzzy/os/drivers/frotz/.git must

be

> here, like this:
> 
>         (cd os/drivers/frotz && git init && git add . && git commit)
> 
> And then that is added as a submodule to the superproject.
> 
> >       git add os/drivers/frotz ;# to the top-level superproject!!
> >
> > to add the "frotz driver" submodule directly to the superproject,

then we

> > could leave /s/xyzzy/os/.git intact, letting it follow the open

source

> > world. Because the superproject must be forked in order to keep

track of

> > what happens in the appliance that supports the "frotz" driver

anyway,

> > this could result in the minimum amount of forking from the end

user's

> > point of view.
> >
> ........
> >

How about 
- creating a "driver" project in the superproject, 
- add a .gitignore or .git/exclude entry for the
/s/xyzzy/os/drivers/frotz folder into the os project
- symlinking the /s/xyzzy/os/drivers/frotz folder to the
/s/xyzzy/driver/frotz folder