Crate git_transport
source ·Expand description
An implementation of the git
transport layer, abstracting over all of its versions, providing
connect()
to establish a connection given a repository URL.
All git transports are supported, including ssh
, git
, http
and https
, as well as local repository paths.
Feature Flags
Mutually Exclusive Client
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 --all-features
.
-
blocking-client
— If set, blocking implementations of the typical git transports become available incrate::client
-
http-client
— Impliesblocking-client
, and adds support for the http and https transports. -
http-client-curl
— Implieshttp-client
, and adds support for the http and https transports using the Rust bindings forlibcurl
. -
async-client
— If set, an async implementations of the git transports becomes available incrate::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 basedgit
transport leaving you with the responsibility to providing such an implementation offutures-io::AsyncRead/AsyncWrite
yourself.
Other
-
serde1
— Data structures implementserde::Serialize
andserde::Deserialize
. -
async-std
— If used in conjunction withasync-client
, theconnect()
method will become available along with supporting the git protocol over TCP, where the TCP stream is created using this crate.
Re-exports
pub use bstr;
pub use git_packetline as packetline;
Modules
Enums
Traits
Functions
blocking-client
and (blocking-client
, or async-client
and async-std
)url
.