All git transports are supported, including
https, as well as local repository paths.
The client portion of transport can be blocking or async. If none is selected, it will be missing entirely.
Specifying both causes a compile error, preventing the use of
blocking-client— If set, blocking implementations of the typical git transports become available in
blocking-client, and adds support for the http and https transports using the Rust bindings for
async-client— If set, an async implementations of the git transports becomes available in
crate::client. Suitable for implementing your own transports while using git’s way of communication, typically in conjunction with a custom server. Note that the blocking client has a wide range of available transports, with the async version of it supporting only the TCP based
gittransport leaving you with the responsibility to providing such an implementation of
serde1— Data structures implement
The version of the way client and server communicate.
The kind of service to invoke on the client or the server side.
A general purpose connector connecting to a repository identified by the given