Talking to a custom git server that has a separate quota for
negotiation:
$ git fetch origin; # https://<something>
fatal: git fetch_pack: expected ACK/NAK, got 'ERR User Is Over Quota'
fatal: The remote end hung up unexpectedly
Three buglets:
i. there's a s/-/_/ typo (and has always been, since v0.99~80, 2005-07-04).
ii. it would be nice to handle the ERR packet instead of showing it as an
internal error (git archive --remote already accepts an ERR packet
in the analagous context.)
iii. why the 'remote end hung up unexpectedly' message after fetch-pack
has already printed a message and died?
(ii) could be handled with a patch like the following: