Commits

Commit:
4c4ce67b628a0b29afb50487072e667ee37e1dad
From:
Stefan Sperling <stsp@stsp.name>
Date:
fix assignment to wrong pointer in got_ref_dup() ok naddy
diff | patch | tree
Commit:
838b0131d8d64c37bbb7caaeba7c23fc018fb941
From:
Stefan Sperling <stsp@stsp.name>
Date:
bump version number
diff | patch | tree
Commit:
22cbd110a84356ef531788b7f5ad19070fc8b3cb
From:
Stefan Sperling <stsp@stsp.name>
Date:
CHANGES for 0.46
diff | patch | tree
Commit:
9a02f8b79138972ddde059e5683108d07b409289
From:
Stefan Sperling <stsp@stsp.name>
Date:
switch to strerror_r(3) in error.c for thread-safety
diff | patch | tree
Commit:
c884fd0a8efbd1c76504f46ddb5b688134983a3a
From:
Stefan Sperling <stsp@stsp.name>
Date:
introduce got_custom_error array to support multiple errors in flight This is still not thread-safe but at least avoids errors overwriting each other in single-threaded contexts.
diff | patch | tree
Commit:
ccf6dd5ee6c1143dcf745ddc604e192389882a38
From:
Stefan Sperling <stsp@stsp.name>
Date:
avoid signed vs unsigned comparisons in fetch.c ssizeof() macro idea courtesy of millert@ ok millert@
diff | patch | tree
Commit:
c156c7a4f456c171f9e458793a2baa06389f8e1e
From:
Stefan Sperling <stsp@stsp.name>
Date:
do not mix up repositories if tog's -r option is used inside a work tree with input from and ok naddy
diff | patch | tree
Commit:
5a8b373cd01671285df647379299fbc5f49707c1
From:
Stefan Sperling <stsp@stsp.name>
Date:
fix parsing of tag objects which lack a tag message This problem could be triggered with the u-boot repository: $ git clone --bare https://gitlab.denx.de/u-boot/u-boot.git $ got log -r u-boot.git got-read-pack: bad object data got: bad object data $
diff | patch | tree
Commit:
e8bfb8f3994fa8096bf56db895d969b4961f8b4b
From:
Stefan Sperling <stsp@stsp.name>
Date:
fix path existence check in got_object_tree_path_changed() A symptom of this was a segfault in 'got blame distrib/miniroot/install.sub' with the OpenBSD src.git from github, reported by jrick. The problem was that the commit graph traversed one commit too far. This could be more easily reproduced with 'got log': got log -c 05f568 -P distrib/miniroot/install.sub Which listed two commits instead of just the first one: 05f568ecc6aadefa1aff9064a29e798874a71409 <-- install.sub first created here 7c0d87f00e480cdf004324dad6f3e6f4418f8f42 "distrib/miniroot" exists in 7c0d87f00e480cdf004324... but not in the parent of this commit. Ensure that we traverse the full path in tree1 even if an intermediate tree2 cannot be opened. Instead of reporting success and a file change if we can't traverse further through tree2, we now hit this failing attempt to open the file 'install.sub' in tree object 180aa33df8d1 (tree1): te1 = find_entry_by_name(tree1, seg, seglen); if (te1 == NULL) { err = got_error(GOT_ERR_NO_OBJ); goto done; } fix tested and ok jrick
diff | patch | tree
Commit:
a4153d5b903b1fe20edad776a6d0ec3c3cbcc0aa
From:
Stefan Sperling <stsp@stsp.name>
Date:
more concise fix for path_list_reverse_input() crash; suggested by millert
diff | patch | tree
Commit:
8891c2aba6a5f6cd43ab51b67115d4fbd0976f73
From:
Stefan Sperling <stsp@stsp.name>
Date:
fix crash in path_list_reverse_input() after switch to unsigned loop index
diff | patch | tree
Commit:
85f4e1e7d36a206d3861d49c00e207d3e7fcab80
From:
Stefan Sperling <stsp@stsp.name>
Date:
fix the type of variable 'idx' in update_packidx()
diff | patch | tree
Commit:
6059809a13b5d528052e38f84661039e6565f458
From:
Stefan Sperling <stsp@stsp.name>
Date:
use size_t for loop indices to avoid signedness warnings; by emaste@freebsd Same change as 16aeacf7088d, for subdirectories other than lib/
diff | patch | tree
Commit:
6d5a9006ab2a400b488b9e93ec9647fb9b2a0930
From:
Yang Zhong <yzhong@freebsdfoundation.org>
Date:
add fd field to got_repository, modify got_packidx_open to use fds These changes are intended to make got more compatible with FreeBSD's Capsicum. ok stsp
diff | patch | tree
Commit:
a615e0e7796ea1103a6e0d4b5dbb613459788666
From:
Stefan Sperling <stsp@stsp.name>
Date:
implicitly mark all files in work tree as up-to-date after rebase/histedit This should always be correct, since rebase and histedit start out with a clean and single-base-commit worktree, and end up committing all changes across the entire work tree when they are successful. tested by jrick and myself
diff | patch | tree