mirror of
https://github.com/martinvonz/jj.git
synced 2025-05-28 10:31:14 +00:00
b9e4e4fe8a
This makes it clear that the repo state isn't mutated during computation of the destination and descendants. Still compute_move_commits() is big, so we might want to split it further. If needed, maybe we can add variants of apply_move_commits() to fix up intermediate predecessor chains? compute_move_commits() needs (immutable) &MutableRepo because it depends on repo.find_descendants_for_rebase().