I've found that the problem was backported into the stable stream since
I cannot reproduce the issue with 2.6.26 but I can with 18.104.22.168. This
is quite useful since there are only 3 relevant looking changesets in
that range. I will bisect between these before confirming the culprit on
I've had a private reply from someone who is seeing the same issue with
22.214.171.124 against a server running 2.6.18 (Debian Etch) which I think
largely discounts the server from being at fault.
Everything ends badly. Otherwise it wouldn't end.