Re: [PATCH 6/6] Teach core object handling functions about gitlinks
- From
- Torgil Svensson <torgil.svensson@gmail.com>
- Date
- Apr 12, 2007, 00:42 UTC
- Message-ID
- <e7bda7770704111742i2ac12cbas50fd7a3ba5c21cd8@mail.gmail.com>
- In-Reply-To
- <Pine.LNX.4.64.0704101122510.6730@woody.linux-foundation.org>
On 4/10/07, Linus Torvalds <torvalds@linux-foundation.org> 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.
Show 7 quoted lines
> [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.