You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Cargo.toml
+12-28
Original file line number
Diff line number
Diff line change
@@ -41,14 +41,15 @@ max = ["max-control", "fast", "gitoxide-core-tools-query", "gitoxide-core-tools-
41
41
42
42
## Like `max`, but only Rust is allowed.
43
43
##
44
-
## This is the most compatible build as it won't need a C compiler or C toolchains to build. It's also not the fastest as or the most feature-rich in terms of available
45
-
## transports as it uses Rust's HTTP implementation.
44
+
## This is the most compatible build as it won't need a C compiler or C toolchains to build. Thanks to zlib-rs, you don't have to trade off between compatibility and performance.
45
+
##
46
+
## This uses Rust's HTTP implementation.
46
47
##
47
48
## As fast as possible, with TUI progress, progress line rendering with auto-configuration, all transports available but less mature pure Rust HTTP implementation, all `ein` tools, CLI colors and local-time support, JSON output, regex support for rev-specs.
#! ZIP might not compile on all platforms, so it depends on the end-user who compiles the application to chose these based on their needs.
221
221
222
222
## Activate features that maximize performance, like using threads, but leave everything else that might affect compatibility out to allow users more fine-grained
223
-
## control over performance features like which `zlib*` implementation to use.
## Activate features that maximize performance, like usage of threads, `and access to caching in object databases, skipping the ones known to cause compile failures
228
-
## on some platforms.
229
-
## Note that this configuration still uses a pure Rust zlib implementation which isn't the fastest compared to its C-alternatives.
230
-
## No C toolchain is involved.
227
+
## Deprecated: gix always uses zlib-rs, so this is equivalent to `max-performance`
231
228
max-performance-safe = ["max-control"]
232
229
233
230
## The tempfile registry uses a better implementation of a thread-safe hashmap, relying on an external crate.
0 commit comments