On Sun, Oct 07, 2007 at 10:59:18PM -0500, Manoj Srivastava wrote: > On Mon, 8 Oct 2007 02:55:37 +0200, Frank Lichtenheld <[EMAIL PROTECTED]> > said: > > Lets not exagerate. At least for git the repository will usually be > > smaller or only little larger than the working directory. It will > > probably compress worse though. > How is this magic done? If I have several dozen feature > branches, all feeding back and forth, and have made lots and lots of > changes in my sources, how does git preserve all this information > without a commensurate increase in size? This makes the information > theory geek in me very very skeptical.
By already using compression in the repository and by aggressively storing data as delta against earlier versions (both for binary and textual data). > Or are you talking about "typical" usage, and is that why people > go around making "shallow" copies to cut down on the size of the > shipped repo? Shallow copies are not a very typical thing to do, IME. Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
