Commits


fix NULL deref with T keymap on log view worktree entry When the log view T keymap is used, the selected_entry is passed to browse_commit_tree() to open a tree view of the repository as at the selected commit, which passes the selected_entry->id member to open_tree_view() to open the commit. The id member, which is a NULL pointer in work tree entries, is dereferenced so we segfault. If the T keymap is used on a work tree entry, use the base commit id instead, which we must have if a work tree entry is selected. ok stsp@


bump version number


CHANGES for 0.107


sync dist file list


do not leak privsep_child memory allocations if sending a stop command fails


make got-read-pack clear its imsgbuf on exit


make got-send-pack clear its imsgbuf on exit


make got-read-tree clear its imsgbuf before exiting in an error case


make got-read-tag clear its imsgbuf on exit in an error case


make got-read-pack clear its imsgbuf before exiting in error cases


make got-read-object clear its imsgbuf before exit in an error case


make got-read-gotconfig clear its imsgbuf before exit in an error case


make got-read-gitconfig clear its imsgbuf before exit in an error case


make got-read-commit clear its imsgbuf before exiting in an error case


make got-read-blob clear its imsgbuf before exiting in an error case


make got-index-pack clear its imsgbuf on exit to avoid leak reports


make got-fetch-pack clear its imsgbuf before exiting to avoid leak reports


plug imsgbuf-related memory leak in got_repo_load()


store ibuf used by got_gotconfig_read() on the stack


store ibuf used by got_repo_read_gitconfig() on the stack


plug imsgbuf-related memory leak in got_send_pack()


store ibuf used by got_patch() on the stack rather than the heap


do not leak ibuf memory in got_patch()


plug imsgbuf-related memory leak in got_repo_index_pack()


plug imsgbuf-related memory leaks in got_fetch_pack()