Commit Briefs

6f23baec62 Stefan Sperling

declare got_clone() in public API space


82bde4e0c8 Stefan Sperling

remove unused header include


afa77e0373 Stefan Sperling

actually create a pack and an index in the right place


279090e148 Stefan Sperling

pass an object_id * to got_privsep_send_index_pack_req()


22b6b4901a Stefan Sperling

add a .git suffix to cloned repositories by default




83b416ed85 Stefan Sperling

add ori as author





8baa7d2656 Stefan Sperling

retry on Z_BUF_ERROR in got_inflate_read() as well




7b1f04a644 Tracey Emery

remove 'Next' link from tags on summary page where no tags exist and commit briefs have set gw_trans->next_id

if gw_briefs set gw_trans->next_id in gw_summary, it was being carried over to gw_tags, causing the 'Next' link to be displayed.



ef6337de1a Stefan Sperling

bump version number


cff5d32f5a Stefan Sperling

change for 0.29


15341bfd54 Tracey Emery

trim directories in got remove -R

This is a racy solution that needs to be properly implemented in the future. ok stsp


5b87815ed2 Stefan Sperling

prevent commits from being listed more than once in a histedit script

While merging a commit multiple times during a histedit operation could potentially make sense in some corner case, a commit appearing more than once in the script is more likely to happen accidentally. If desired, the same effect can still be achieved by running multiple histedit operations, or by using 'got cherrypick' while the histedit operation is paused for arbitrary editing.


de05890fef Stefan Sperling

fix histedit 'rebase commit ID mismatch' error when splitting a commit

Commit IDs on histedit's temporary branch can change arbitrarily because the user may create new commits on this branch while editing past commits. So there is no point in trying to verify these IDs like we do during rebase. Add a test case which demonstrates the problem.


4cb8f8f3e6 Stefan Sperling

fix wrong use of words in a histedit error message


37486c756a Stefan Sperling

make our README file point at our website


4b6c9460c9 Stefan Sperling

be helpful when users try to check out work trees without a known branch

Provide a useful error message in such cases and explicitly document intentional restrictions in the got(1) man page. Prompted by a question from Adam Steen via bsd.network https://bsd.network/@adams/103768951483318235