Commits


plug memory leaks in error paths while collecting log messages


check for errors from write(2) and close(2) while collecting log messages


add per-worktree got.conf(5) file in the .got directory; ok millert


use plain write() in place of dprintf() with a pre-formatted string step-by-step guidance from millert; ok millert stsp


zap trailing tabs


add got.conf(5) configuration file ok tracey


actually make use of an intermediate variable in cmd_clone() found by tracey's scan-build


add -s option to 'got remove' which deletes files in a particular status This makes it easy to deal with files that were deleted from disk by external tooling which modified the work tree. Such files are left in missing (!) status and can now be marked for deletion in bulk via 'got rm -s\! -R .' For consistency, modified (M) files can now be removed with 'got rm -s M' which implies 'got rm -f'. Prompted by feedback from krw@


add -s option to 'got status' which acts as a status code filter Advantages over using grep are that the list of codes is validated against a list of known status codes, and that it is easier to match staged files which can display status codes in one or both of two columns. Prompted by feedback from krw@


make 'got log' -R and -P options work in combination With -R, the -P option did not show any paths. Regression test added here demonstrates the problem.


Add a 'got info' command which displays work tree meta-data. Remove the alias 'got in' for 'got init'. The 'in' alias was too close to either 'init' or 'info'. ok tracey, millert


forbid bad symlinks; add -S option to 'got commit' and 'got stage' to allow them


make 'got diff' show changes to symlinks in a work tree


show path in error message when blaming a symlink pointing to a directory


add symlink support to 'got blame' and 'tog blame'