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

From: Sam Vilain <sam@vilain.net>
Date: Apr 11, 2007, 23:36 UTC
Message-ID: <461D70E1.10901@vilain.net>
In-Reply-To: <200704101828.37453.Josef.Weidendorfer@gmx.de>

Josef Weidendorfer wrote:

Show 7 quoted lines

> An example for such an attribute would be a subproject name/ID.
> An argument for this: The user should be able to specify some policies
> for submodules, like "do not clone/checkout this submodule". But the
> path where the submodule resides in a given commit is not useful here,
> as a submodule can reside at different paths in the history of the
> supermodule.
>

I mentioned this briefly on another strand of this thread, but I think that the simplest way to do this would be to just make refs/subproject/* populate itself sensibly when you commit in the superproject.

I mentioned refs/subprojects/path/branch before, but I think it would probably be the sort of thing that should be in the .git/config

Sam.