Commits


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@


fix a use-after-free in get_changed_paths() in got and tog Once the parent commit is closed the tree_id1 pointer is no longer valid, but the pointer was still being used. Make a deep copy to fix this issue.


plug a small memory leak in tog's show_diff_view() function


prevent a race where 'gotadmin cleanup' deletes concurrently created objects


track the last modification time of references


bump version number