kernel/git - git - PowerEL Git System

Tree: 65b5e41e24

Author	SHA1	Message	Date
Linus Torvalds	f846bbff15	git-pack-objects: make "--window=x" semantics more logical. A zero disables delta generation (like before), but we make the window be one bigger than specified, since we use one entry for the one to be tested (it used to be that "--window=1" was meaningless, since we'd have used up the single-entry window with the entry to be tested, and had no chance of actually ever finding a delta). The default window remains at 10, but now it really means "test the 10 closest objects", not "test the 9 closest objects".	20 years ago
Linus Torvalds	75c42d8cc3	Add a "max_size" parameter to diff_delta() Anything that generates a delta to see if two objects are close usually isn't interested in the delta ends up being bigger than some specified size, and this allows us to stop delta generation early when that happens.	20 years ago
Linus Torvalds	78817c15de	Fix delta "sliding window" code When Junio fixed the lack of a successful error code from try_delta(), that uncovered an off-by-one error in the caller. Also, some testing made it clear that we now find a lot more deltas, because we used to (incorrectly) break early on bogus "failure" cases.	20 years ago
Junio C Hamano	eb41ab11e8	[PATCH] (patchlet) pack-objects.c: try_delta() Return value of try_delta is checked for negativeness, but the success path does not return anything, letting compiler warn and presumably return garbage. Signed-off-by: Junio C Hamano <junkio@cox.net> Signed-off-by: Linus Torvalds <torvalds@osdl.org>	20 years ago
Linus Torvalds	d38c3721a1	git-pack-objects: mark the delta packing with a 'D'. When writing a delta, we take the real type from the object we're doing the delta against, and just write a 'D' as the type of the current object.	20 years ago
Linus Torvalds	49397104f2	git-pack-objects: fix typo ("<" should be "=")	20 years ago
Linus Torvalds	c323ac7d9c	git-pack-objects: create a packed object representation. This is kind of like a tar-ball for a set of objects, ready to be shipped off to another end. Alternatively, you could use is as a packed representation of the object database directly, if you changed "read_sha1_file()" to read these kinds of packs. The latter is partiularly useful to generate a "packed history", ie you could pack up your old history efficiently, but still have it available (at a performance hit, of course). I haven't actually written an unpacker yet, so the end result has not been verified in any way yet. I obviously always write bug-free code, so it just has to work, no?	20 years ago

1 2