Re: full kernel history, in patchset format
- From
Petr Baudis <pasky@ucw.cz>
- Date
- Apr 17, 2005, 23:39 UTC
- Message-ID
- <20050417233936.GV1461@pasky.ji.cz>
- In-Reply-To
- <1113780698.11910.8.camel@localhost.localdomain>
Dear diary, on Mon, Apr 18, 2005 at 01:31:36AM CEST, I got a letter where David Woodhouse <dwmw2@infradead.org> told me that...
Show 6 quoted lines
> Note that any given copy of a tree doesn't _need_ to keep all the > history back the beginning of time. It's OK if the oldest commit object > in your tree actually refers back to a parent which doesn't exist > locally. I can well imagine that some people will want to keep their > trees pruned to keep only a few weeks of history, while other copies of > the tree will keep everything.
I think this is bad, bad, bad. If you don't keep around all the _commits_, you get into all sorts of troubles - when merging, when doing git log, etc. And the commits themselves are probably actually pretty small portion of the thing. I didn't do any actual measurement but I would be pretty surprised if it would be much more than few megabytes of data for the kernel history.
Of course an entirely different thing are _trees_ associated with those commits. As long as you stay with a simple three-way merge, you basically never want to look at trees which aren't heads and which you don't specifically request to look at. And the trees and what they carry inside is the main bulk of data.
-- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor