Martin von Zweigbergk 6e302bb3a2 op_store: add a virtual root operation, similar to root commit ... It seems obvious in hindsight to have a virtual root operation just like we have a virtual root commit. It removes the same kind of problems by making sure there's always a common ancestor (or multiple) between any two commits. I think the reason I didn't add a root operation from the beginning was that there used to be a mandatory working-copy commit in the view (this was before support for multiple workspaces). Perhaps we should remove the "initialize repo" operation now. The only difference between their view objects is that the "initialize repo" operation adds the root commit as a head. We could add that to the root operation, but then the root operation's value depends on the commit backend.		2024-01-14 10:15:14 -08: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	op_store: add a virtual root operation, similar to root commit	2024-01-14 10:15:14 -08:00
tests	op_store: add a virtual root operation, similar to root commit	2024-01-14 10:15:14 -08:00
testutils	object_id: extract ObjectId trait and macros to separate module	2024-01-05 10:20:57 +09:00
Cargo.toml	lock: remove byteorder dependency from tests, use fs helper functions	2023-12-23 00:14:17 +09:00
LICENSE	cargo: add LICENSE file to each crate we publish	2023-09-22 21:48:28 -07:00