From: Torgil Svensson Date: Thu, 12 Apr 2007 00:42:43 GMT Subject: Re: [PATCH 6/6] Teach core object handling functions about gitlinks Message-ID: In-Reply-To: On 4/10/07, Linus Torvalds wrote: > - I tend to like "minimal", > - in a "link" object, the only thing that would normally *change* is > really just the commit SHA1. Everything else is really pretty static. I like this concept. > [module "kdelibs"] > dir = kdelibs > url = git://git.kde.org/kdelibs > description = "Basic KDE libraries module" > > [module "base"] > alias = "kdelibs", "kdebase", "kdenetwork" 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? 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.