Commits


gotd.conf: treat repositories without any parameters as a syntax error Because gotd expects some parameters to be present they must not be optional at the syntax level.


gotwebd: remove got_prefix in gotwebd.conf(5) example


fmt


adjust the first gotwebd.8 httpd.conf example to work out of the box gotwebd defaults to listening on a unix socket, and this man page aims to provide an appropriate configuration snippet in EXAMPLES. suggested by Paul Wrankin via gameoftrees IRC


fix previous; name must be initialized otherwise if binaryfilename fails to match the line, `name' may be left pointing to free'd memory.


got patch: handle the removal of binary files Diffs that remove binary files don't have hunks so got patch would skip over them, treating that part of the diff as "noise". Different programs outputs a slightly different diff for this kind of patches, but the "Binary files ... and /dev/null differ" is usually shown, so try to match it. The adedd regress test covers got diff, git diff, and OpenBSD' /usr/bin/diff. CVS diffs will currently fail because the guessed file name will be wrong. CVS prints the file name in the Index and RCS lines which got patch currently ignores, and shows an useless path in the "Binary files /tmp/cvs... and /dev/null differ" line. Discussed with and ok stsp@


gotwebd: print commit message too in gotweb_render_commits Regression from 156a1144 spotted by stsp, thanks!


gotwebd is a Web daemon


farewell, gotweb. you served us well. rm gotweb, ok stsp@


enforce a per-uid connection limit in the gotd listen process For now the limit is set at compile-time. It will become configurable via gotd.conf soon. ok op@


gotwebd: drop redundant NULL check qs is guaranteed to be not NULL reached that point.


gotwebd: remove useless comment should be placed further down, after BLOB and RSS are handled, but the call to `gotweb_render_header' is successfully clear on its own.


fmt


gotd listen process forgot to initialize its client table siphash key


convert gotd repo_read.c and repo_write.c to single-client Because these processes are now started on demand per client connection there is no need to keep track of multiple clients anymore. Also, these processes can now exit when a disconnect event is received. ok op, jamsek