Comment 4 for bug 75721

Scratch that, I meant:

The mentioned patch is similar in the sense that it concerns clone() too.

But even without that patch, in the http case, the connection was still shared.

Only the range_hints was lost, which means that bzr, in the worst case, may have to rediscover that the server can't handle ranges but will do so with the *same* connection.

Anyway, I think John is on the right track, multiple connections means either a bug in the cloning process or a failure to call clone.