Releases 1

pull brings a working copy that fell behind up to its bookmark (issue #89). The working copy followed a pull only from exactly the bookmark's old heads, and not at all when the pull brought nothing new, so one left behind by bookmark set, a landing or a pull from another workspace stayed on old code while status said clean. It now follows whenever its base is part of the bookmark's state, clean or carrying uncommitted work, and status says when the working copy is behind its bookmark and by how many changes.

Faster merges in a Git import (issue #80). A merge is built from only the paths it can change, as an ordinary commit is: on VS Code at 139 000 commits merges import 3.2 times faster (9.5 s against 30.9 s on average) and the import as a whole 2.7 times faster, with exactly the history the whole-tree path builds. OXY_IMPORT_WHOLE_MERGES=1 takes the old path.

A binary file changed and made executable at once keeps both (issue #87). oxy commit and the Git import dropped the executable bit when a binary file got new contents in the same change.

Several remotes and no origin (issue #83). core.remote names the default remote; bookmark list compares with a remote that has the bookmark and names it; the error without a default says what to do.

No i386 notice from apt (issue #85). The .deb's apt source names the machine's own architecture, and an upgrade adds it to a source written before, so a system with i386 enabled no longer warns on every update.

Clearer messages. A missing author identity says which config set it and how to pin the right one (issue #82); oxy git verify --max-differences N and a summary of what differs by kind.