Re: [RFC] Submodules in GIT

From: Jakub Narebski <jnareb@gmail.com>
Date: Dec 2, 2006, 13:08 UTC
Message-ID: <ekrtph$6nh$1@sea.gmane.org>
In-Reply-To: <45706758.2020907@b-i-t.de>

Stephan Feder wrote:

> That's it: There is no need for a separate branch or repository. If you 
> have the subproject's commit in the superproject's object database (and 
> we really have that, see 1. and 2. above), why do you _have to_ store it 
> elsewhere?

It would be much simpler to have subproject's commit in subproject object database, and have it available in superproject's object database by the way of alternates.

Otherwise when commiting new submodule state in supermodule you would have to fetch all the needed objects (submodule mighe have evolved few commits in history inbetween) into superproject's object database.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

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