Commits

Commit:
f2c5fe0e01b265dfe66dfa19e99e5a30cd738363
From:
Stefan Sperling <stsp@stsp.name>
Date:
no need to zero memory in got_inflate_to_mem_fd()
diff | patch | tree
Commit:
d1078c40c0a28790e906d27e22df90d0337e6002
From:
Stefan Sperling <stsp@stsp.name>
Date:
add a TODO item
diff | patch | tree
Commit:
691332ddca35e907929b2a6acd099dea5c0ab08d
From:
Stefan Sperling <stsp@stsp.name>
Date:
increase GOT_INFLATE_BUFSIZE (trades memory usage for speed)
diff | patch | tree
Commit:
6dc3b75a27a79e74c8221bd260f619fe58ca4619
From:
Stefan Sperling <stsp@stsp.name>
Date:
no need to zero memory in got_inflate_to_mem()
diff | patch | tree
Commit:
b48e2ddb7c7f3bec51c4be31a1484677022384e8
From:
Stefan Sperling <stsp@stsp.name>
Date:
set datasize limit of got-read-pack helpers to maximum
diff | patch | tree
Commit:
1a35c1bc90d05a6bac56e2602a0bcc2109796fce
From:
Stefan Sperling <stsp@stsp.name>
Date:
fix double-frees in error path when resolving deltas fails
diff | patch | tree
Commit:
78527a0aa079d64a0cbe7def60d689e2fef5beb5
From:
Stefan Sperling <stsp@stsp.name>
Date:
move a comment to a better place and expand it
diff | patch | tree
Commit:
cc79381d1af8e783b6164745018a174399f46004
From:
Stefan Sperling <stsp@stsp.name>
Date:
NUL-terminate empty logmsg buffer for strlcat(3) Because the logmsg output buffer was not NUL-terminated after allocation, strlcat(3) could append log message contents copied from the temporary file at a wrong memory location. In the case observed by me, this bug resulted in a broken commit object.
diff | patch | tree
Commit:
d4592c7c7aa8a7bf2d09aeb096625941be8bd1e3
From:
Stefan Sperling <stsp@stsp.name>
Date:
catch fopen(3) failure in collect_commit_logmsg()
diff | patch | tree
Commit:
c932eeeb83c00ba282780d657b539e342d092311
From:
Stefan Sperling <stsp@stsp.name>
Date:
make 'got update' bump the base commit ID of unchanged files This change makes it actually possible to get around commit-time out-of-dateness by running 'got update'. The test added with this commit shows that our out-of-dateness check is currently too simplistic; an update is required between any two commit operations! It would be better to allow commits to proceed until a situation arises where file content must be merged.
diff | patch | tree
Commit:
e4d984c230e887c67692cfcbb7624ab2ccf95e2d
From:
Stefan Sperling <stsp@stsp.name>
Date:
expand test coverage: partial update with parent dir as argument
diff | patch | tree
Commit:
b03c880f032f7cfc88a56c2ede174663d4357344
From:
Stefan Sperling <stsp@stsp.name>
Date:
fix handling of non-directories in change from previous commit
diff | patch | tree
Commit:
941e9f741afacc0a0b0fc19b80c534c8917589fb
From:
Stefan Sperling <stsp@stsp.name>
Date:
tog: if opened from log view, open tree view at path being logged
diff | patch | tree
Commit:
8cbe58099b1488354d3efbfcb9f4877ed5b1364c
From:
Stefan Sperling <stsp@stsp.name>
Date:
plug /dev/null file descriptor leaks in diffreg.c
diff | patch | tree
Commit:
8656d6c4d5273b7a838b8d2b0b057891e50a2ece
From:
Stefan Sperling <stsp@stsp.name>
Date:
make struct got_commitable opaque to library users
diff | patch | tree