Martin von Zweigbergk 33bf6ce1d5 view: don't force commits pointed to by refs to be current heads ... If you rewrite a commit that's also available on some remote, you'll currently see both the old version and the new version in the view, which means they're divergent. They're not logically divergent (the rewritten version should replace the old version), so this is a UX bug. I think it indicates that the set of current heads should be redefined to be the *desired* heads. That's also what I had suspected in the TODO removed by this change. I think another indication that we should hide the old heads even if they have e.g. a remote branch pointing to them is that we don't want them to be rebased if we rewrite an ancestor. So that's what I decided to do: let the view's heads be the desired heads. The user can still define revsets for showing non-current commits pointed to by e.g. remote branches.		2021-10-23 09:15:05 -07:00
..
benches
protos	backend: remove unused Commit::is_pruned (#32)	2021-10-06 23:53:15 -07:00
src	view: don't force commits pointed to by refs to be current heads	2021-10-23 09:15:05 -07:00
tests	view: don't force commits pointed to by refs to be current heads	2021-10-23 09:15:05 -07:00
build.rs
Cargo.toml	cargo: update test-case to 1.2.0 now that frondeus/test-case#66 is fixed	2021-06-28 12:13:14 -07:00