Re: Gitweb and submodules
- From
- Sven Verdoolaege <skimo@kotnet.org>
- Date
- Jul 29, 2007, 16:37 UTC
- Message-ID
- <20070729163747.GJ31114MdfPADPa@greensroom.kotnet.org>
- In-Reply-To
- <200707282239.29340.jnareb@gmail.com>
On Sat, Jul 28, 2007 at 10:39:28PM +0200, Jakub Narebski wrote:
Show 9 quoted lines
> On Sat, 28 July 2007, Sven Verdoolaege wrote: > > On Sat, Jul 28, 2007 at 12:29:16PM +0200, Jakub Narebski wrote: > >> It has to be configuration variable because the > >> location of repository which has submodule objects doesn't change when > >> checking out (or rewinding) to different commit in supermodule. > > > > Let's hope Pasky provides a way to set this information... > > Why Pasky?
I was thinking about projects on repo.or.cz. We'd want to have a way to specify the locations of submodules.
Show 6 quoted lines
> I am thinking about the following sequence to search for submodule > objects: > > From $GIT_DIR/config: > submodule.$name.objects (absolute or relative to gitdir of superproject) > submodule.$name.gitdir (absolute or relative to gitdir of superproject)
Do we really need both of these?
Show 5 quoted lines
> submodule.$name.url (to find GIT_DIR, if it is local filesystem URL) > > If there is working directory, from .gitmodules file in top level > of working directory: > submodule.$name.path/.git (relative to toplevel of working directory)
Having a relative path for the URL in .gitmodules in a public repo doesn't seem very useful to me. I know it's only meant as a default value, but if it is a relative path, then it won't work for anyone cloning the superproject.
skimo