Commits


remove github capabilities workaround from got-send-pack, it is not needed This workaround was inherited from git9, which claims that Github did not send capabilities. Protocol traces show that Github's server does in fact advertise its capabilities. Git protocol capabilities are hidden behind a NUL byte in the middle of the first refline sent by the server. This makes them easy to miss when treating a refline as a C string. I guess this is why Ori concluded that Github didn't send any capabilities. Or perhaps Github has been fixed since.


remove unused name variables, noticed by naddy@


clean up weird grammar. not sure what i was thinking.


fix to allow empty send and fetch blocks, ok stsp@


add send and fetch plumbing to parser for got.conf This is the beginning of support for naddy's suggestion to break this out similar to git. More code to come from stsp. ok stsp@


allow deletion of refs/remotes/ branches with got branch -d Also, make requirements for branch name arguments more flexible. Absolute reference names are now accepted. ok naddy@


more manual page updates following the introduction of 'got send'


small man page spelling fixes


update the TODO list


tweak the man page section about 'got send' In particular, attempt to describe the -f option better.


fix the output of 'got send -d' upon success Previous output was: Already up-to-date New output is: Server has deleted refs/heads/branch Check this behavour in the related regression test.


Use POSIX-compatible syntax in send.sh tests. Patch by naddy@


add 'got send' command for sending changes to remote repositories Known to work against git-daemon and github Git server implementations. Tests by abieber, naddy, jrick, and myself. Man page additions reviewed by Lucas.


use POSIX [ s1 = s2 ] syntax instead of [ s1 == s2 ]


add a missing bounds-check in got-fetch-pack when parsing server response The tokenize_refline() function could end up reading past the end of the buffer if the refline is not terminated with whitespace or \0.


prevent NULL deref in got-fetch-pack if server does not announce capabilities The my_capabilities pointer may remain NULL. Check for NULL before use.


fix the error message shown when the server sends a bad ref line Exposed by trying to run got clone -l against shithub.us over git:// found by abieber@


Expose got_ref_name_is_valid() for general purpose use. This will be needed for a future 'got send' command.


fix miscalculation of the final pack file size reported by got_pack_create()


expose got_ref_resolve_symbolic() at the public library API This will be needed by a future 'got send' command.


plug a memory leak in an error path of got_deltify()


make got_deltify() rellocate the deltas array less often


style fix: avoid comparison of pointer variable against 0 in got-fetch-pack


remove unused 'repo' argument from got_reflist_insert()


use less memory allocations when formatting log messages Rewrite got_object_commit_get_logmsg() such that only one memory allocation is made when creating a pretty version of a log message. ok naddy@