- 18 Feb, 2016 3 commits
-
-
Fix a typo
Carlos Martín Nieto committed -
Carlos Martín Nieto committed
-
`compatability` → `compatibility`
Prayag Verma committed
-
- 16 Feb, 2016 3 commits
-
-
commit: expose the different kinds of errors
Carlos Martín Nieto committed -
We should be checking whether the object we're looking up is a commit, and we should let the caller know whether the not-found return code comes from a bad object type or just a missing signature.
Carlos Martín Nieto committed -
rebase: persist a single in-memory index
Carlos Martín Nieto committed
-
- 15 Feb, 2016 1 commit
-
-
When performing an in-memory rebase, keep a single index for the duration, so that callers have the expected index lifecycle and do not hold on to an index that is free'd out from under them.
Edward Thomson committed
-
- 11 Feb, 2016 7 commits
-
-
rebase: introduce bare rebasing
Carlos Martín Nieto committed -
Horrible fix for #3173.
Edward Thomson committed -
Arthur Schreiber committed
-
When we moved the logic to handle the first one, wrong loop logic was kept in place which meant we still finished early. But we now notice it because we're not reading past the last LF we find. This was not noticed before as the last field in the tested commit was multi-line which does not trigger the early break.
Carlos Martín Nieto committed -
Coverity improvements for GITERR_CHECK_ALLOC
Carlos Martín Nieto committed -
Allow callers of rebase to specify custom merge options. This may allow custom conflict resolution, or failing fast when conflicts are detected.
Edward Thomson committed -
Introduce the ability to rebase in-memory or in a bare repository. When `rebase_options.inmemory` is specified, the resultant `git_rebase` session will not be persisted to disk. Callers may still analyze the rebase operations, resolve any conflicts against the in-memory index and create the commits. Neither `HEAD` nor the working directory will be updated during this process.
Edward Thomson committed
-
- 10 Feb, 2016 2 commits
-
-
When posting our instrumented build results to Coverity we have to include sensitive information, in particular our authorization token. Currently we use an unencrypted channel to post this information, leading to the token being transferred in plain. Fix this by using a secured connection instead.
Patrick Steinhardt committed -
Coverity currently lists a lot of errors with regard to GITERR_CHECK_ALLOC causing resource leaks. We know this macro is only invoked when we want to abort because we are out of memory. Coverity allows for overriding the default model where we know that certain functions guarantee a desired behavior. The user_nodefs.h is used to override the behavior of macros. Re-define GITERR_CHECK_ALLOC inside of it to specify its abort nature.
Patrick Steinhardt committed
-
- 09 Feb, 2016 15 commits
-
-
Introduce git_commit_extract_signature
Vicent Marti committed -
Coverity fixes
Carlos Martín Nieto committed -
This returns the GPG signature for a commit and its contents without the signature block, allowing for the verification of the commit's signature.
Carlos Martín Nieto committed -
commit: also match the first header field when searching
Carlos Martín Nieto committed -
Patrick Steinhardt committed
-
Patrick Steinhardt committed
-
Patrick Steinhardt committed
-
Patrick Steinhardt committed
-
The function `git_packfile_stream_open` tries to free the passed in stream when an error occurs. The only call site is `git_indexer_append`, though, which passes in the address of a stream struct which has not been allocated on the heap. Fix the issue by simply removing the call to free. In case of an error we did not allocate any memory yet and otherwise it should be the caller's responsibility to manage it's object's lifetime.
Patrick Steinhardt committed -
We were searching only past the first header field, which meant we were unable to find e.g. `tree` which is the first field. While here, make sure to set an error message in case we cannot find the field.
Carlos Martín Nieto committed -
Coverity fixes
Carlos Martín Nieto committed -
Better document `git_merge_commits` redux
Carlos Martín Nieto committed -
`git_merge_commits` and `git_merge` now *do* handle recursive base building for criss-cross merges. Remove the documentation that says that they do not. This reverts commit 5e44d9bc.
Edward Thomson committed -
mailmap: add ethomson@github.com
Edward Thomson committed -
Edward Thomson committed
-
- 08 Feb, 2016 2 commits
-
-
When copying contents of the cURL certiinfo we duplicate the data but forget to actually put it into the vector.
Patrick Steinhardt committed -
Patrick Steinhardt committed
-
- 07 Feb, 2016 1 commit
-
-
Introduce Contributor Covenant
Carlos Martín Nieto committed
-
- 05 Feb, 2016 3 commits
-
-
Free allocated pointer to curl stream on error
Carlos Martín Nieto committed -
winhttp: name mangle class / iid on mingw
Edward Thomson committed -
Export git_stash_apply_init_options
Edward Thomson committed
-
- 04 Feb, 2016 3 commits
-
-
Fix typo
Edward Thomson committed -
Ephemera committed
-
Fix a typo in documentation
Edward Thomson committed
-