Commits

Commit:
e1e77cc43b61294facdf656a456a4108c13eb638
From:
Stefan Sperling <stsp@stsp.name>
Date:
in got_opentempfd() don't attempt to unlink the file if mkstemp(3) failed
diff | patch | tree
Commit:
ee0cb6f251ce4466cdb6e46c69c773e1891eb30b
From:
Stefan Sperling <stsp@stsp.name>
Date:
allow inflate(3) to consume all mapped data at once in got_inflate_read_mmap()
diff | patch | tree
Commit:
8baa7d2656b89e5d4536a655d0e6cfacdf32549a
From:
Stefan Sperling <stsp@stsp.name>
Date:
retry on Z_BUF_ERROR in got_inflate_read() as well
diff | patch | tree
Commit:
afbfc7fb1894f033414e690ac1e2260b5b2c79d8
From:
Stefan Sperling <stsp@stsp.name>
Date:
remove unneeded memory allocations from ref delta parser which were leaking
diff | patch | tree
Commit:
686d24ff4f3d55e87e66b7ea741be79aadcfa5b0
From:
Stefan Sperling <stsp@stsp.name>
Date:
Z_BUF_ERROR is not fatal; try to decompress more data when it happens
diff | patch | tree
Commit:
7b1f04a64481938488cb6031cc765f593cee5aed
From:
Tracey Emery <tracey@traceyemery.net>
Date:
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.
diff | patch | tree
Commit:
3969253a0514c1e4c685eb413d74cd89f40ecaf0
From:
Stefan Sperling <stsp@stsp.name>
Date:
remove implicit entry update from got_fileindex_entry_alloc(); just alloc
diff | patch | tree
Commit:
ef6337de1aa046d1d1aac4bea349644ba9a0f649
From:
Stefan Sperling <stsp@stsp.name>
Date:
bump version number
diff | patch | tree
Commit:
cff5d32f5a46800c1429011dad94c5b20b28501c
From:
Stefan Sperling <stsp@stsp.name>
Date:
change for 0.29
diff | patch | tree
Commit:
15341bfd54bbabbe30297c358faf41ee05e247da
From:
Tracey Emery <tracey@traceyemery.net>
Date:
trim directories in got remove -R This is a racy solution that needs to be properly implemented in the future. ok stsp
diff | patch | tree
Commit:
5b87815ed2f346f81374261ce2d633feae711886
From:
Stefan Sperling <stsp@stsp.name>
Date:
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.
diff | patch | tree
Commit:
de05890fef951240ac68a3ea9a577a6f82be6194
From:
Stefan Sperling <stsp@stsp.name>
Date:
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.
diff | patch | tree
Commit:
4cb8f8f3e6cc4a795c92823235070dd921c2b42e
From:
Stefan Sperling <stsp@stsp.name>
Date:
fix wrong use of words in a histedit error message
diff | patch | tree
Commit:
37486c756a36ae590b41cae752b0c129f5fb7ff7
From:
Stefan Sperling <stsp@stsp.name>
Date:
make our README file point at our website
diff | patch | tree
Commit:
4b6c9460c99283f193f32bd5177bb09047abacf3
From:
Stefan Sperling <stsp@stsp.name>
Date:
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
diff | patch | tree