Commits


fix a bug where 'got status' showed an unchanged empty file as changed


make 'got histedit' collapse folded add+delete operations into a no-op If a merged commit wants to delete a locally added file, and this locally added file matches the content which was deleted in the commit being merged, we can go ahead with the deletion because there is no risk of data loss. fixes the histedit problem reported by jrick on freenode


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


use modern POSIX timestamp fields in struct stat ok stsp


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@


fix committing file additions from a work tree with a path prefix New files were added under the wrong tree in the repository if the work tree has a path prefix. Fix this problem and catch it in the existing commit_with_path_prefix regression test.


fix spurious 'got cherrypick' error with a path prefix and an empty tree If the work tree's path prefix does not exist in the first of the two trees, then 'got cherrypick' failed with "no such entry found in tree". But this is a legitimate situation, as shown in the new test added here. The first tree could be the empty tree, for example, which should result in 'got cherrypick' adding all files from the second tree instead of complaining about a non-existent path-prefix directory in the first tree.


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


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


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


rename get_symlink_status() to get_symlink_modification_status() for clarity


use a shortcut in get_file_status() for detecting symlinks appearing on disk


move deeply indented code from unstage_path() to a new unstage_hunks() helper


make 'got unstage -p' work with symlinks


remove merge_blob() fallback from merge_symlink(); let callers handle this


stop reinstalling symlinks after commit; 'got update' can handle that


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


put checks for bad symlink target paths into a dedicated function


make 'got unstage' work with symlinks


stop using realpath(3) to resolve a symlink target in install_symlink() We should not resolve a symlink target path recursively when installing a symlink in the work tree. We want to handle this symlink's target, not the end result of following a chain of symlinks in case such links already exist.


add support for symlinks to 'got revert -p'


make 'got stage -p' work with symlinks


fix wrong function name in an error message


set a staged file type and handle it separately from the on-disk file type


make staging of symlinks work