Commits


add test coverage for tog displaying a symlink


Fix for cc1: warnings being treated as errors /home/got/src/got/tog/tog.c: In function 'draw_tree_entries': /home/got/src/got/tog/tog.c:7307: warning: comparisons like X<=3DY<=3DZ do = not have their mathematical meaning


add kill_repo_proc() similarly to the other kill_*_proc() ok stsp@


reword user-facing error message which mentions "fast-forward" For user-facing messages it is better to avoid technical jargon like this and instead spell out what the fast-forward situation implies: that one branch is already based on another. ok jamsek


typo


missing semicolon... sigh I can't assume I can blindly add one simple line.


move gotd_child_proc to gotd.c make it opaque since it's unused outside of gotd.c. While here, drop the unused `nhelpers' field. ok/tweak stsp@


tweak wording in got.1 which suggested that use of rebase was mandatory


explain why the first 'got clone' example in got.1 will often fail


provide a 'got merge' example in the EXAMPLES section of got.1


prevent 'got merge' from creating commits on branches outside of "refs/heads/" ok op, james


make installation prefix info more visible in README


make 'got add' more forgiving about unversioned paths on the command line When users run 'got add *' the shell may pick up already versioned files and trigger errors about paths being in an unexpected status. Expand the check which previously only allowed files in added status to be double-added to cover the following status codes which are all safe to ignore: A M C m This should make bulk additions of files a bit easier in most cases. Problem reported by robert@ ok jamsek


expand test coverage of test_double_add a bit more


Implement fast-forward merges. Split part of got_worktree_merge_prepare into a new function, got_worktree_merge_write_refs, since that part doesn't make sense in the fast-forward case. ok stsp@