Commits


show base commit hash and omit filenames in conflict markers


handle xbit-only changes during 'got update'


show original file content in conflict markers


indicate non-existent paths in 'got status' and make 'got diff' error for them


add support for tags to -c options of some got commands


fix typo in test commit log message


relax commit out-of-dateness check: consider file content only


make 'got update' accept mulitple path arguments


fix a status bug exposed by test_update_conflict_wt_rm_vs_repo_rm


don't report base-bump-only updates as 'already up to date'


relax out-of-dateness check for 'got commit'


fix sandbox name used by test_update_bumps_base_commit_id


consistently use leading upper-case for messages indicating success


make moved branch head references easier to deal with


improve wording of an error message


inform the user when switching branches


make 'got update' bump the base commit ID of unchanged files This change makes it actually possible to get around commit-time out-of-dateness by running 'got update'. The test added with this commit shows that our out-of-dateness check is currently too simplistic; an update is required between any two commit operations! It would be better to allow commits to proceed until a situation arises where file content must be merged.


expand test coverage: partial update with parent dir as argument


make 'got update' verify that provided commit and branch match


add branch support to 'got update'


use cmp -s, instead of cmp, in all command line tests


fix linear ancestry verification check for 'got update'


add support for partial updates, which affect specific paths only


add a test for wt rm vs repo rm


don't leave file as unversioned in case of wt edit vs repo rm