Martin von Zweigbergk fd4146d485 backend: use new enum for Commit::root_tree ... We currently represent the root tree id in a commit by `Merge<TreeId>` plus a boolean `uses_tree_conflict_format`. It's better to use an enum for that. That makes it harder to forget to check which type of tree it is, and it makes it impossible to store a legacy tree with multiple ids (as we could with `uses_tree_conflict_format=false`, `root_tree=Merge::new(...)`). Maybe more importantly, we're also going to want to pass around this information in most places where we currently pass a single `TreeId`, and passing two separate values would be annoying.		2023-08-26 07:02:04 -07:00
..
benches	cargo: rename crates from jujutsu/jujutsu-lib to jj-cli/jj-lib	2023-07-09 06:40:43 +02:00
gen-protos	Use { workspace = true } to appease VS Code's Cargo.toml parser	2023-08-22 21:38:53 -07:00
src	backend: use new enum for Commit::root_tree	2023-08-26 07:02:04 -07:00
tests	merged_tree: in diff iterator, maintain legacy/modern variant in subtree	2023-08-26 05:58:54 -07:00
testutils	Use { workspace = true } to appease VS Code's Cargo.toml parser	2023-08-22 21:38:53 -07:00
Cargo.toml	merged_tree: add diff iterator	2023-08-25 06:40:36 -07:00