Fix issues when cloning repositories with large blobs (>4GB)

[LordKiRon]

This PR fixes a couple of problems when cloning large repositories (in my case, a 67GB database containing 4GB+ versioned files). This fixes the clone/fetch, but working with the repository still fails, only much later :)

[dscho]

@LordKiRon I would like to upstream this fix, but upstream Git requires a real name in the Signed-off-by line. Would you mind providing that?

[LordKiRon]

@LordKiRon I would like to upstream this fix, but upstream Git requires a real name in the Signed-off-by line. Would you mind providing that?

Sorry , but this creates ties between my real life and public activity I would like to avoid. Not that I am doing something illigal or unpropriete in either area :) and I guess after some digging on the net you might even connect my nickname to my real name, but its a different than creating real connection.
I preffer to keep "internet life" and personal life separate.

[dscho]

@LordKiRon I would like to upstream this fix, but upstream Git requires a real name in the Signed-off-by line. Would you mind providing that?

Sorry , but this creates ties between my real life and public activity I would like to avoid. Not that I am doing something illigal or unpropriete in either area :) and I guess after some digging on the net you might even connect my nickname to my real name, but its a different than creating real connection. I preffer to keep "internet life" and personal life separate.

Understood. I'll take ownership, publicly, then, documenting that you are the actual author but prefer to stay pseudonymous.

[dscho]

I have cleaned up the patches and rebased them onto v2.54.0, and submitted them to the upstream Git project over here: gitgitgadget#2102.

[dscho]

Ouch. That's not what I meant. By mistake, I pushed the wrong branch, sorry!