Re: [RFC] Submodules in GIT

From: Sven Verdoolaege <skimo@kotnet.org>
Date: Dec 8, 2006, 18:45 UTC
Message-ID: <20061208184532.GE940MdfPADPa@greensroom.kotnet.org>
In-Reply-To: <1165602554.19135.309.camel@cashmere.sps.mot.com>

On Fri, Dec 08, 2006 at 12:29:14PM -0600, Jon Loeliger wrote:

Show 8 quoted lines

> Why not have a "glue" object at the "stub"-interface of
> the supermodule tree that provides policy mappings to
> the sub-modules.  Perhaps indicating git URL location,
> mappings of branch names between super- and sub- modules,
> special commit SHA1s, user policy or config choices at
> the boundary, and things like that.
> 
> Is that the sort of direction we are headed?

Not unless you have something useful in mind that could be put in these glue objects. URLs and branch names, in particular, should not be stored in the repository itself, but in configuration files, since they will be different for different copies of the repo.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.