Yuya Nishihara cd173059dc cli: op diff: sort modified changes purely by commit ids ... This basically means that the graph is sorted by "new" commits, then abandoned commits follow. I'm thinking of integrating predecessors information into "op diff", and it will make sense to identify changes by commit ids instead of change ids there. Divergent commits will be displayed individually, and squashed commits will have all predecessor commits including ones having different change ids. This should also fix "graph has cycle" issue. In the original implementation, we mixed parent change ids of both new and old views, which could result in cycle.		2025-06-12 10:33:57 +00:00
..
examples	store: Add Send bounds to the AsyncRead future returned by read_file	2025-06-09 21:08:10 +00:00
src	cli: op diff: sort modified changes purely by commit ids	2025-06-12 10:33:57 +00:00
testing	diff: Run external diff tools in their temp dir	2025-05-12 21:34:19 +00:00
tests	cli: op diff: sort modified changes purely by commit ids	2025-06-12 10:33:57 +00:00
build.rs	build: fix cargo publish by symlinking cli/docs->docs	2024-11-05 17:37:14 -08:00
Cargo.toml	cargo: Add metadata to build .deb package with cargo-deb	2025-06-08 20:18:57 +00:00
docs	build: fix cargo publish by symlinking cli/docs->docs	2024-11-05 17:37:14 -08:00
LICENSE	cargo: add LICENSE file to each crate we publish	2023-09-22 21:48:28 -07:00