forked from mirrors/jj
revset: use unstable sort to enforce ordering of commit ids
This wouldn't matter in practice, but there should be no reason to stick to stable sort.
This commit is contained in:
parent
bac2de6ac6
commit
d04556cf18
1 changed files with 1 additions and 1 deletions
|
@ -717,7 +717,7 @@ fn revset_for_commit_ids<'index>(
|
||||||
for id in commit_ids {
|
for id in commit_ids {
|
||||||
index_entries.push(index.entry_by_id(id).unwrap());
|
index_entries.push(index.entry_by_id(id).unwrap());
|
||||||
}
|
}
|
||||||
index_entries.sort_by_key(|b| Reverse(b.position()));
|
index_entries.sort_unstable_by_key(|b| Reverse(b.position()));
|
||||||
index_entries.dedup();
|
index_entries.dedup();
|
||||||
Box::new(EagerRevset { index_entries })
|
Box::new(EagerRevset { index_entries })
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in a new issue