Commits


simplify the error message shown when 'got rebase' has nothing to do


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


implicitly mark all files in work tree as up-to-date after rebase/histedit This should always be correct, since rebase and histedit start out with a clean and single-base-commit worktree, and end up committing all changes across the entire work tree when they are successful. tested by jrick and myself


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


add a test for rebase file index corruption problem fix in previous commit ok tracey


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


use 'got commit' in test_rebase_delete_missing_file instead of Git


add a test for 'got rebase' to check behaviour on delete vs. delete


add -c option to 'got ref' which now expects just one argument after options


show merged commit ID + logmsg upon merge conflict during rebase and histedit This makes it more apparent which commit contained the conflicting change. The new output looks like this: C sys/dev/pci/if_iwm.c 8a98d848a1a5 -> merge conflict: properly modify station queues got: conflicts must be resolved before rebasing can continue


let 'got branch' switch and update the work tree ok tracey


add a test which ensures that 'got rebase' trims empty dirs from disk


add copyright year for files already touched in 2020


prevent rebase with an out-of-date work tree


if there are no commits to rebase, just forward the rebased branch's reference Problem found by kn@


show base commit hash and omit filenames in conflict markers


show original file content in conflict markers


fix behaviour of 'got rebase' with no commits to rebase; with semarie@


fix and test interaction of rebase/histedit -c and 'got stage'


tweak 'got rebase' conflict error message


fix wrong sandbox name used by a rebase test


fix extra whitespace in rebased log messages Trim leading and trailing whitespace from log messages when creating commits. Fixes a rebase issue but should be a good idea in general.


prevent rebase in a work tree with an incompatible path prefix


disallow 'got update' and 'got commit' while rebase is in progress