Commits


do not update symlinks which are already up-to-date This fixes spurious 'U' notifications for symlinks during 'got update' that occurred even when the work tree was fully up-to-date. Observed on a work tree of the FreeBSD src repo and reproduced in our test suite by adding a no-op update at the end of a test which deals with updating symlinks.


expand coverage of test_update_single_file: test file deletion during update


fix copy-pasta in test_update_single_file


fix bug where 'got up -c commit path' deleted unrelated files from work tree Problem reported by Timo Myyrä


use POSIX [s1 = s2] syntax instead of [s1 == s2]; patch by Ryo ONODERA


consistently label removed files as "/dev/null" in diff headers


switch function declarations from Korn shell to Bourne/POSIX shell syntax ok stsp


add a -q option to tests for quiet output and use it for 'make regress' Previous default output remains when test cases are run individually. ok tracey


display more context info in "no such entry found in tree" error messages


remove the symlink conflict header feature; it causes noise for little benefit


handle additional symlink conflicts and report skipping of unversioned files


handle symlink deletion and symlink conflicts during 'got update'


add symlink support to 'got update'


add submodule tests ok semarie


show a summary of conflicts and related problems after updating/merging files ok millert@


make 'got update' skip conflicted files ok millert@


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