read-only git repositories
- From
- David Lang <david.lang@digitalinsight.com>
- Date
- May 5, 2005, 09:51 UTC
- Message-ID
- <Pine.LNX.4.62.0505050231300.15451@qynat.qvtvafvgr.pbz>
- In-Reply-To
- <200505050709.43307.alan@chandlerfamily.org.uk>
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.
possible uses of this would be to have a bunch of data on read-only media (say the 3G+ kernel history on a DVD), having a pruned local object store with automated fetching from elsewhere if the object isn't found locally, or marking the object store that you plan on sharing with the world as read-only (with your changed object going into a secondary store) so that you don't pollute it accidently (this could also cut down on the storage requirements)
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.
David Lang
-- There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies. -- C.A.R. Hoare