Commits


changes for 0.33


assign 'ret' explicitly in test_commit_normalizes_filemodes


normalize tree entry modes to 0100644 or 0100755 when writing tree objects semarie@ reported an error from go-git used by Cirrus CI: "57243613255d758e15b0f5ae1c960b970f0435f8: malformed mode (0100640)!" 'git fsck' has no problem with mode 0100640. But writing just the two most commonly used file modes should provide the best compatibility.


fix "searching..." displayed in tog log view while merely scrolling down


remove a redundant .Pp in got.1 (found by mandoc -T lint)


in got.1, clarify how 'got update' deals with local (aka uncommitted) changes


bump version number


changes for 0.32


be nice to unaware users who attempt to use got commands with a Git work tree


show 'searching...' during 'tog log' search even if no new commits are loaded


display "no matches found" if no commit matches a 'tog log' search


display "no more matches" indicator if 'tog log' search cannot find any


make 'tog log' consistently scroll one page upon page-down key (found by naddy)


make 'got fetch' restore our copy of the remote HEAD if the copy was deleted


make 'got fetch -d' delete branches from both refs/heads and refs/remotes


bump version number


changes for 0.31


sync dist file list


set the executable bit on tree.sh


make 'got fetch' update our copy of the remote HEAD in case it has changed


fix got_ref_change_symref(); it changed the ref's name instead of its target


make 'got clone' create refs/remotes/origin/HEAD, as 'git clone' does


handle refs/remotes/origin/HEAD properly; reported by Matthias aka _xhr_


stop verifying pack file checksum in the main process during clone/fetch Both got-fetch-pack and got-index-pack now verify the pack file checksum. This means we can avoid reading the entire pack file in the main process just to verify its checksum and avoid a noticable stall between fetching and indexing on slow machines.


make got-index-pack check the expected pack checksum passed from main process