Re: [RFC] Submodules in GIT

From: Andy Parkins <andyparkins@gmail.com>
Date: Dec 1, 2006, 19:17 UTC
Message-ID: <200612011917.19252.andyparkins@gmail.com>
In-Reply-To: <45706758.2020907@b-i-t.de>

On Friday 2006, December 01 17:33, Stephan Feder wrote:

> 1. A submodule is stored as a commit id in a tree object.
>
> 2. Every object that is reachable from the submodule's commit are
> reachable from the supermodule's repository.

I'm still not convinced about 2. Why should any of the submodule commits be in the supermodule repository? I know that is what you've implemented, but it still feels like too much of a blending of the submodule into the supermodule.

In fact, why should the submodule commits be even visible in the supermodule? That tree->submodule commit is sufficient; there isn't any need to view submodule history in the supermodule.

Andy

-- 
Dr Andrew Parkins, M Eng (Hons), AMIEE

$ 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.