Lukas Wunner [off-list ref] writes:
On Wed, May 20, 2020 at 03:40:19PM -0400, Jeff King wrote:
quoted
The "too big fetch" issue has since been fixed in "master", as well as
reverting the switch to the v2 protocol (which I think is just
belt-and-suspenders; AFAIK there are no known issues after the fix).
Both will be in v2.27. I don't see anything on "maint", but they _could_
be part of an eventual v2.26.3.
The fix was merged in 0b07eecf6e (Merge branch 'jt/v2-fetch-nego-fix',
2020-05-01) for reference.
Please consider cutting a v2.26.3 release with this fix at your
earliest convenience. The waste of bandwidth is mind-boggling.
(> 1 GByte whenever fetching from a kernel remote.)
In the meantime, v2.27.0 rc2 will be out tomorrow. Please consider
helping us polish it by testing that version.
Thanks.