Hi Selma, Bensaid, Selma wrote: > FYI, we are observing the same issue today on chromium coreboot repo > https://chromium-review.googlesource.com/admin/repos/chromiumos/third_party/coreboot > I think we need to figure out a proper solution.
Thanks for providing the debug output! So since the issue does stem from a large distance between branches and hitting network communication limits maybe an effective workaround would be to maintain a local clone of the upstream repo (in a separate repo) and using a file:// URL pointing to that repo for the origin remote in your working repo? The upstream clone must be on the same machine, so it's more overhead, but file:// should be reliable. HTTP, regardless of version, is really inappropriate for applications. //Peter _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
