Re: [PATCH 6/6] Teach core object handling functions about gitlinks

From: Martin Waitz <tali@admingilde.org>
Date: Apr 12, 2007, 00:56 UTC
Message-ID: <20070412005654.GQ21701@admingilde.org>
In-Reply-To: <e7bda7770704111742i2ac12cbas50fd7a3ba5c21cd8@mail.gmail.com>

hoi :)

On Thu, Apr 12, 2007 at 02:42:43AM +0200, Torgil Svensson wrote:

Show 5 quoted lines

> I guess this file could also cover the case where the superproject is
> only interested in a small subset of the subproject. For example if I
> only uses some header-files in a library and want
> "/lib1/src/interface" in the subproject end up as "/includes/lib1" in
> the superproject. Could single files be handled in a similar way?

Conceptionally this information would have to be part of the supermodule tree (after all it changes how your tree is set up).

I think it makes more sense to make users think about which part of their tree can be reused and make them choose submodule boundaries wisely so that the above partial-checkout is not needed.

Show 5 quoted lines

> Although this is just an example, external links shouldn't be
> specified in the same configuration file as project internal things
> (which should be version-controlled). If the url configuration gets
> overwritten with checkouts there will be problems bisecting if the url
> changes over time.

Most of the time we may not need to add any per-submodule URL information anyway. If you fetch a new supermodule version, you can get the new submodule from the same source (or from a per-submodule source which can be determined by looking at and munching the supermodule URL).

-- 
Martin Waitz