Waleed Khan c7b677b86d build: switch back to gix/max-performance-safe feature by default ... Using `gix/max-performance` requires `cmake` as a build-time dependency, which could be a significant barrier for contributors (including existing ones, like me, who already work on jj but didn't have `cmake` installed thus far). This commit switches back to using `gix/max-performance-safe`, which doesn't have the `cmake` dependency, and adds `gix/max-performance` behind the `gix-max-performance` feature for `jj-lib`. It also adds `gix-max-performance` to the `packaging` feature group, since I'm assuming that packagers will want maximum performance, and are more likely to have `cmake` at hand. Tested with ``` $ cargo build --workspace $ cargo build --workspace --features packaging ``` (and the `--features packaging` build failed until I installed `cmake`)		2024-12-31 17:07:52 -06:00
..
examples	repo: remove &UserSettings argument from new/rewrite_commit(), use self.settings	2024-12-31 10:51:57 +09:00
src	repo: remove &UserSettings argument from new/rewrite_commit(), use self.settings	2024-12-31 10:51:57 +09:00
testing	merge_tools: add "$marker_length" variable	2024-12-23 08:42:10 -06:00
tests	config: preserve key formatting on set_value()	2024-12-29 09:57:04 +09:00
build.rs	build: fix cargo publish by symlinking cli/docs->docs	2024-11-05 17:37:14 -08:00
Cargo.toml	build: switch back to gix/max-performance-safe feature by default	2024-12-31 17:07:52 -06:00
docs	build: fix cargo publish by symlinking cli/docs->docs	2024-11-05 17:37:14 -08:00
LICENSE