Commits


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


make 'got update' skip conflicted files ok millert@


add a test for 'got cherrypick' with existing merge conflicts


add 'got log' -x option to stop logging when a specific commit was traversed


wrap an overlong line


add script which runs build and regress and sends failure reports via email


handle all khttp_urlpart errors


Add minimum kcgi version information to README


remove all asprintf from gw_output_site_link and fix error handling


remove all asprintf from gw_output_repo_heads


reduce asprint usage in gw_output_repo_tree


remove all asprintf from gw_blame_cb


remove all asprintf from gw_output_repo_tags


remove all asprintf from gw_tags


remove all asprintf from gw_briefs


remove all asprintf from gw_commits


remove all asprintf from gw_index


use khtml_printf where possible


use khttp_printf where possible


bump version number


changes for 0.33


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.


fix "searching..." displayed in tog log view while merely scrolling down


remove a redundant .Pp in got.1 (found by mandoc -T lint)