forked from mirrors/jj
1f27a78957
I think it's better to let the caller decide if the parents should be added. One use case for removing a head is when fetching from a Git remote where a branch has been rewritten. In that case, it's probably the best user experience to remove the old head. With the current semantics of `View::remove_head()`, we would need to walk up the graph to find a commit that's an ancestor and for each commit we remove as head, its parents get temporarily added as heads. It's much easier for callers that want to add the parents as heads to do that. |
||
|---|---|---|
| .. | ||
| test_bad_locking.rs | ||
| test_commit_builder.rs | ||
| test_commit_concurrent.rs | ||
| test_diff_summary.rs | ||
| test_evolution.rs | ||
| test_git.rs | ||
| test_index.rs | ||
| test_init.rs | ||
| test_load_repo.rs | ||
| test_merge_trees.rs | ||
| test_operations.rs | ||
| test_transaction.rs | ||
| test_view.rs | ||
| test_working_copy.rs | ||
| test_working_copy_concurrent.rs | ||