Re: [PATCH] {fetch,receive}-pack: skip sha-1 integrity test on objects from new pack
From: Nguyen Thai Ngoc Duy <hidden>
Date: 2016-06-15 22:53:19
Possibly related (same subject, not in this thread)
- 2016-06-15 · Re: [PATCH] {fetch,receive}-pack: skip sha-1 integrity test on objects from new pack · Junio C Hamano <hidden>
- 2016-06-15 · Re: [PATCH] {fetch,receive}-pack: skip sha-1 integrity test on objects from new pack · Nguyen Thai Ngoc Duy <hidden>
- 2016-06-15 · Re: [PATCH] {fetch,receive}-pack: skip sha-1 integrity test on objects from new pack · Junio C Hamano <hidden>
- 2016-06-15 · Re: [PATCH] {fetch,receive}-pack: skip sha-1 integrity test on objects from new pack · Nguyen Thai Ngoc Duy <hidden>
- 2016-06-15 · Re: [PATCH] {fetch,receive}-pack: skip sha-1 integrity test on objects from new pack · Junio C Hamano <hidden>
2012/3/16 Junio C Hamano [off-list ref]:
Following the above train of thought, the patch to revert what 6d4bb38 (fetch: verify we have everything we need before updating our ref, 2011-09-01) did which caused this performance regression should look like this. "tag --contains 6d4bb38" tells me that this affects everything since v1.7.8-rc0 so we may want to issue maintenance updates once this proves good in 1.7.10. Nguyễn, sorry for being dense. I think this ended up being very close to your initial patch.
I have cheaper "git fetch" any way. That's all that counts from my user point of view :) What about push/receive-pack? I think the same thing happens there. -- Duy