peer-or-repo: build a peer directly in the `peer` function
We skip the ambiguous _peerorrepo function to explicitly build a peer within
the dedicated function. This mean explicitly getting a peer from an explicitly
create repository when necessary.
static-http: have `statichttprepo.instance` return a peer object
It previously returned a statichttprepo object which could not be used for
anything but creating a peer. So lets put it into the peer bucket with a peer
behavior.
scheme: move the drive letter checking in its own function
This help the readability of the main function as is was taking much more room
than the main logic.
peer-or-repo: split the scheme between repo and peer
Some of the scheme will always produce a peer and some will always produce a
repository. So lets use different mapping to reduce the ambiguity.
peer-or-repo: stop relying on AttributeError in `islocal`
This will confused pytypes in a future changeset.
repo-or-peer: deprecate calling `islocal` on non-path object
There object have a `.local()` method and should use it.
tests: add the missing space to test-hghave.t (
issue6762)
log() in run-tests.py add a space to the end of all messages that it prints,
and I missed this fact in my previous patch.