Commits


make 'got update' display the worktree's branch name upon success ok tracey


use the POSIX-compliant "date -u" command to return UTC time; ok stsp


add missing "return 1" to failure handling in the regress scripts ok stsp@


fix hang in commit regress test. ok stsp


add 'got commit -F' option to commit with a log message stored in a file To avoid accidents commit -F opens the prepared log message in an editor so it can be reviewed before the commit is created. For non-interactive use the -N option is required in addition to -F. ok millert@


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


expand arguments in shell script since brace expansion is not in POSIX ok stsp


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


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


add got.conf(5) configuration file ok tracey


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


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.


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


extend test_commit_symlink test case


make it possible to fix "bad" symlinks with ln -sfh + got commit + got update


remove debugging test code


convert bad symlinks to regular files during 'got commit'


add symlink support to 'got commit'


fix unintended change of current working directory in a test case


allow creation of commits which carry unmodified submodule tree entries along approach suggested by ori@ and matches how git9 behaves ok semarie@ (who can now work with Rust-related Git repos containing submodules)


add submodule tests ok semarie


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


assign 'ret' explicitly in test_commit_normalizes_filemodes


normalize tree entry modes to 0100644 or 0100755 when writing tree objects semarie@ reported an error from go-git used by Cirrus CI: "57243613255d758e15b0f5ae1c960b970f0435f8: malformed mode (0100640)!" 'git fsck' has no problem with mode 0100640. But writing just the two most commonly used file modes should provide the best compatibility.