Commits


gotd and got {fetch,send,clone}: reject sha256 repos We have to implement the gitprotocol v2 in order to support sha256 repos for these operations, so for now let's error out early when they're attempted. ok/improvements stsp@


rename "sha1" field to "hash" done with X ,x/\.sha1/c/.hash X ,x/->sha1/c/->hash in sam after loading all the C files; except for one manual tweak in hash.c


ensure we properly zero got_object_id structs ok tobeh@


gotd: use a struct got_object_id instead of an hash buffer ok stsp@


display abbreviated commit/tag IDs in email notification subject lines This should make it somewhat easier to keep track of discussion threads when someone replies to a commit notification to discuss the changes.


gotd_request_timeout() should use log_warnx() since errno is not used here


ensure gotd request timeout gets armed even if no request is received


raise log level of message that is logged when a gotd request times out


make gotd notifications work when 'git push' is used instead of 'got send' Git clients disconnect earlier, which resulted in session_write exiting before notifications were sent. Do not treat early EOF as a fatal error if we are sending notifications. Add regression test coverage for 'git push'. Problem found by Thomas Adam.


expose authenticated gotd user account in HTTP notifications ok op@


gotd: don't ignore error in session_dispatch_repo_child ok stsp


display process title in syslog when a gotd child process exits


split gotd/session.c into session_read.c and session_write.c This makes it easier to tweak the read/write code paths separately.