Re: read-only git repositories (ancient history)

From: David A. Wheeler <dwheeler@dwheeler.com>
Date: May 6, 2005, 03:01 UTC
Message-ID: <427ADDEC.3060709@dwheeler.com>
In-Reply-To: <Pine.LNX.4.62.0505050231300.15451@qynat.qvtvafvgr.pbz>

David Lang wrote:

> given that git already treats everything in the object storage as being 
> fixed it occured to me that there may be value in makeing it so that git 
> can make use of more then one pool of storage

...

> there are probably other uses and it seems like a fairly small 
> modification to add a hook to use if the object isn't found initially 
> that I thought I'd mention it to the group.

Reasonable. Another use would be to have a repository with "ancient history" (e.g., Linux pre-2.6) that isn't normally loaded or looked at, but COULD be looked at if you added that repository. For that use, though, you'd need a way to record "the parent of X is Y" since the information creating connections BETWEEN the repositories might not be stored in the later repository itself (see the discussions about Linux kernel history recreation).

--- David A. Wheeler