forked from mirrors/jj
36ee24379b
The idea is that the "remote" refs could have been "op restore"-d whereas view.git_refs() will never be. The next commit will update known_remote_refs to be constructed from the current remote branches. Instead of building these lists in a single loop, we could load new git_refs to the view first, and then build diffs of the remote refs. I considered that, but I feel it would be a bit awkward to update refs before importing commits to the view. The "remote" refs are stored in BTreeMap since merging order should be stable. |
||
|---|---|---|
| .. | ||
| benches | ||
| gen-protos | ||
| src | ||
| tests | ||
| testutils | ||
| Cargo.toml | ||
| LICENSE | ||