- 05 Oct, 2018 1 commit
-
-
Patrick Steinhardt committed
-
- 06 Aug, 2018 1 commit
-
-
Patrick Steinhardt committed
-
- 05 Jul, 2018 1 commit
-
-
Patrick Steinhardt committed
-
- 06 Jun, 2018 1 commit
-
-
Patrick Steinhardt committed
-
- 29 May, 2018 3 commits
-
-
Patrick Steinhardt committed
-
These can't go into the public API yet as we don't want to introduce API or ABI changes in a security release.
Carlos Martín Nieto committed -
Carlos Martín Nieto committed
-
- 11 Mar, 2018 1 commit
-
-
Carlos Martín Nieto committed
-
- 08 Mar, 2018 1 commit
-
-
Jacques Germishuys committed
-
- 02 Mar, 2018 1 commit
-
-
Jacques Germishuys committed
-
- 23 Feb, 2018 1 commit
-
-
By placing docs per enum value rather than in a large block, the automated doc generation tool can make nicer docs, as could other automated tools, such as the mooted https://github.com/libgit2/git2go/issues/427. The current rendering is somewhat ugly: https://libgit2.github.com/libgit2/#HEAD/type/git_pathspec_flag_t No textual changes, just reorganization.
Josh Bleecher Snyder committed
-
- 20 Feb, 2018 1 commit
-
-
Patrick Steinhardt committed
-
- 02 Feb, 2018 1 commit
-
-
The streaming read functionality should provide the length and the type of the object, like the normal read functionality does.
Edward Thomson committed
-
- 22 Jan, 2018 1 commit
-
-
Fixes #4492, #4496.
Adrián Medraño Calvo committed
-
- 21 Jan, 2018 1 commit
-
-
Allow for a custom conflict marker size, allowing callers to override the default size of the "<<<<<<<" and ">>>>>>>" markers in the conflicted output file.
Edward Thomson committed
-
- 19 Jan, 2018 1 commit
-
-
We used to hard-code the octothorpe as the comment character and the documentation still mentions this even though we accept the comment character as a parameter. Update the line to indicate this and clean up the first paragraph a bit.
Carlos Martín Nieto committed
-
- 17 Jan, 2018 2 commits
-
-
Brian Lopez committed
-
Brian Lopez committed
-
- 12 Jan, 2018 1 commit
-
-
References passed to the callback function of `git_reference_foreach` are expected to be owned by the callback. As such, they are never being freed by `git_reference_foreach`, but will have to be freed by the caller. This small detail is never mentioned in the function's documentation, though, making it easy to get wrong. Document this to make it discoverable.
Patrick Steinhardt committed
-
- 04 Jan, 2018 1 commit
-
-
Brian Lopez committed
-
- 31 Dec, 2017 1 commit
-
-
The documentation for `git_treebuilder_insert` erroneously states that we do not validate that the entry being inserted exists. We do, as of https://github.com/libgit2/libgit2/pull/3633. Update the documentation to reflect the new reality.
Edward Thomson committed
-
- 19 Dec, 2017 1 commit
-
-
This is implemented in trailer.c and borrows a large amount of logic from Git core to ensure compatibility.
Charlie Somerville committed
-
- 30 Nov, 2017 1 commit
-
-
David Catmull committed
-
- 25 Nov, 2017 1 commit
-
-
I'm not sure if worktree.h was intentionally left out of git2.h. Looks like an oversight since it is in fact documented.
apnadkarni committed
-
- 19 Nov, 2017 1 commit
-
-
We default to off, but we might want to consider changing `GIT_DIFF_NORMAL` to include it.
Carlos Martín Nieto committed
-
- 18 Nov, 2017 1 commit
-
-
We do it the same as git does: case-sensitively on the normalized form of the variable name. While here also specify that we're case-sensitive on the values when handling the values when setting or deleting multivars.
Carlos Martín Nieto committed
-
- 12 Nov, 2017 1 commit
-
-
Git considers '-0000' a valid offset for signature lines. They need to be treated as _not_ equal to a '+0000' signature offset. Parsing a signature line stores the offset in a signed integer which does not distinguish between `+0` and `-0`. This patch adds an additional flag `sign` to the `git_time` in the `signature` object which is populated with the sign of the offset. In addition to exposing this information to the user, this information is also used to compare signatures. /cc @pks-t @ethomson
Henry Kleynhans committed
-
- 10 Nov, 2017 1 commit
-
-
optios -> options
Ken Dreyer committed
-
- 09 Oct, 2017 2 commits
-
-
Our current configuration logic is completely oblivious of any repository, but only cares for actual file paths. Unfortunately, we are forced to break this assumption by the introduction of conditional includes, which are evaluated in the context of a repository. Right now, only one conditional exists with "gitdir:" -- it will only include the configuration if the current repository's git directory matches the value passed to "gitdir:". To support these conditionals, we have to break our API and make the repository available when opening a configuration file. This commit extends the `open` call of configuration backends to include another repository and adjusts existing code to have it available. This includes the user-visible functions `git_config_add_file_ondisk` and `git_config_add_backend`.
Patrick Steinhardt committed -
Several functions to retrieve variables from a repository only return immutable values, which allows us to actually constify the passed-in repository parameter. Do so to help a later patch, which will only have access to a constant repository.
Patrick Steinhardt committed
-
- 06 Oct, 2017 6 commits
-
-
This also adds tests for this function.
Richard Ipsum committed -
This also adds tests for this function.
Richard Ipsum committed -
This also adds tests for this function.
Richard Ipsum committed -
This adds a new function that will allow creation of notes without necessarily updating a particular ref, the notes tree is obtained from the git_commit object parameter, a new commit object pointing to the current tip of the notes tree is optionally returned via the 'note_commit_out' parameter, optionally the blob id for the note is returned through the 'note_blob_out' object.
Richard Ipsum committed -
Very many callbacks in libgit2 have some sort of typedef to normalize the name at git_<name_of_operation>_cb. Add a typedef for push_update_references in the remote so the name follows the same conventions.
Carson Howard committed -
Jacob Wahlgren committed
-
- 11 Aug, 2017 1 commit
-
-
Alpha committed
-
- 30 Jul, 2017 1 commit
-
-
Edward Thomson committed
-
- 10 Jul, 2017 1 commit
-
-
Pointers to general data should usually be used as a void pointer such that it is possible to hand in variables of a different pointer type without the need to cast. This is the same when creating patches from buffers, where the buffers may contain arbitrary data. Instead of requiring the caller to care whether his buffer is e.g. `char *` or `unsigned char *`, we should instead just accept a `void *`. This is also consistent in how we tread other types like for example `git_blob`, which also just has a void pointer as its raw contents.
Patrick Steinhardt committed
-
- 30 Jun, 2017 1 commit
-
-
Andrey Davydov committed
-