summaryrefslogtreecommitdiff
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
* rebase: deprecate signing_cbethomson/commit_create_cbEdward Thomson2021-08-293-22/+31
| | | | | The signing callback should not be used; instead, callers should provide a commit_create_cb, perform the signing and commit creation themselves.
* rebase: introduce git_commit_create_cbEdward Thomson2021-08-292-0/+52
| | | | | | | Introduce a new mechanism for `git_rebase_commit` for callers to customize the experience. Instead of assuming that we produce the commit for them, provide a commit creation callback that allows callers to produce the commit themselves and return the resulting commit id.
* amiga: use ';' as path list separator on AmigaOSPeter Pettersson2021-08-081-3/+3
| | | | Like on Windows ':' is used for volume names in absolute paths.
* odb: Implement option for overriding of default odb backend priorityTony De La Nuez2021-07-301-1/+11
| | | | | | | | | | | Introduce GIT_OPT_SET_ODB_LOOSE_PRIORITY and GIT_OPT_SET_ODB_PACKED_PRIORITY to allow overriding the default priority values for the default ODB backends. Libgit2 has historically assumed that most objects for long- running operations will be packed, therefore GIT_LOOSE_PRIORITY is set to 1 by default, and GIT_PACKED_PRIORITY to 2. When a client allows libgit2 to set the default backends, they can specify an override for the two priority values in order to change the order in which each ODB backend is accessed.
* Merge branch 'pr/5861'Edward Thomson2021-07-301-0/+13
|\
| * branch: git branch upstream merge has been exposed.Dmitry Lobanov2021-05-121-0/+13
| |
* | Merge branch 'pr/5940'Edward Thomson2021-07-306-133/+265
|\ \
| * | status: document `GIT_STATUS_OPT_INCLUDE_UNREADABLE`Edward Thomson2021-07-302-29/+75
| | | | | | | | | | | | Document `GIT_STATUS_OPT_INCLUDE_UNREADABLE`, and some minor cleanups.
| * | Fix struct documentation formattingpunkymaniac2021-07-064-86/+158
| | |
| * | Add missing return documentationpunkymaniac2021-07-061-0/+2
| | |
| * | Add missing empty linepunkymaniac2021-07-061-0/+1
| | |
| * | Fix documentation formatting for git_diff_filepunkymaniac2021-07-061-19/+30
| | |
| * | Fix bad char at the end of the wordpunkymaniac2021-07-061-1/+1
| | |
* | | Merge pull request #5952 from libgit2/ethomson/attrs_from_commitEdward Thomson2021-07-293-0/+149
|\ \ \ | | | | | | | | Support reading attributes from a specific commit
| * | | filter: introduce GIT_BLOB_FILTER_ATTRIBUTES_FROM_COMMITEdward Thomson2021-07-222-0/+24
| | | | | | | | | | | | | | | | | | | | Provide a mechanism to filter using attribute data from a specific commit (making use of `GIT_ATTR_CHECK_INCLUDE_COMMIT`).
| * | | attr: introduce GIT_ATTR_CHECK_INCLUDE_COMMITEdward Thomson2021-07-221-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Introduce `GIT_ATTR_CHECK_INCLUDE_COMMIT`, which like 4fd5748 allows attribute information to be read from files in the repository. 4fd5748 always reads the information from HEAD, while `GIT_ATTR_CHECK_INCLUDE_COMMIT` allows users to provide the commit to read the attributes from.
| * | | filter: add git_filter_optionsEdward Thomson2021-07-221-0/+36
| | | | | | | | | | | | | | | | | | | | Allow filter users to provide an options structure instead of simply flags. This allows for future growth for filter options.
| * | | attr: introduce `git_attr_options` for extended queriesEdward Thomson2021-07-221-0/+79
| |/ / | | | | | | | | | | | | | | | | | | Allow more advanced attribute queries using a `git_attr_options`, and extended functions to use it. Presently there is no additional configuration in a `git_attr_options` beyond the flags, but this is for future growth.
* | | Swap the order of the `git_graph_reachable_from_any` paramslhchavez2021-07-271-2/+2
| | | | | | | | | | | | len, array -> array, len
* | | graph: Create `git_graph_reachable_from_any()`lhchavez2021-07-271-2/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change introduces a new API function `git_graph_reachable_from_any()`, that answers the question whether a commit is reachable from any of the provided commits through following parent edges. This function can take advantage of optimizations provided by the existence of a `commit-graph` file, since it makes it faster to know whether, given two commits X and Y, X cannot possibly be an reachable from Y. Part of: #5757
* | | Merge pull request #5765 from lhchavez/cgraph-revwalksEdward Thomson2021-07-263-0/+63
|\ \ \ | | | | | | | | commit-graph: Use the commit-graph in revwalks
| * | | commit-graph: Create `git_commit_graph` as an abstraction for the filelhchavez2021-03-103-0/+63
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change does a medium-size refactor of the git_commit_graph_file and the interaction with the ODB. Now instead of the ODB owning a direct reference to the git_commit_graph_file, there will be an intermediate git_commit_graph. The main advantage of that is that now end users can explicitly set a git_commit_graph that is eagerly checked for errors, while still being able to lazily use the commit-graph in a regular ODB, if the file is present.
* | | | Merge pull request #5890 from lolgear/git_submodule_dupEdward Thomson2021-07-221-0/+9
|\ \ \ \ | |_|/ / |/| | | [Submodule] Git submodule dup
| * | | submodule: git submodule dup out and source parameters have become mandatory.Dmitry Lobanov2021-06-151-1/+1
| | | |
| * | | submodule: git submodule dup documentation has been fixed.Dmitry Lobanov2021-06-011-2/+2
| | | |
| * | | submodule: git submodule dup object dup has been added.Dmitry Lobanov2021-05-261-3/+5
| | | |
| * | | submodule: git submodule dup has been added.Dmitry Lobanov2021-05-161-0/+7
| | |/ | |/|
* | | Merge pull request #5917 from tiennou/fix/docurium-issuesEdward Thomson2021-07-022-0/+2
|\ \ \ | | | | | | | | docs: fix some missing includes that cause Docurium to error out
| * | | docs: fix some missing includes that cause Docurium to error outEtienne Samson2021-05-272-0/+2
| | | |
* | | | Merge pull request #5910 from arxanas/patch-1Edward Thomson2021-06-151-2/+2
|\ \ \ \
| * | | | Update index.hWaleed Khan2021-06-141-2/+2
| | | | |
| * | | | Fix misleading doc for `git_index_find`Waleed Khan2021-06-131-1/+1
| |/ / / | | | | | | | | In https://github.com/libgit2/libgit2/pull/5723/files/fc46dc06f52f854f74371682f911f13856c68edb#r540092847, I was confused by the semantics of `git_index_find`. The documentation says both that it returns the output value in `at_pos` and that it returns it directly as an `int`. This is incorrect; the return value is only returned via `at_pos`.
* | | | Add some missing documentation about return valuepunkymaniac2021-06-022-0/+4
| | | |
* | | | Fix struct indentationpunkymaniac2021-06-021-0/+1
| | | |
* | | | Remove bad space in documentationpunkymaniac2021-06-021-1/+1
| | | |
* | | | Add documentation about GIT_OPT_GET_USER_AGENTpunkymaniac2021-06-021-0/+5
|/ / /
* | | Merge branch 'pr/5853'Edward Thomson2021-05-191-0/+4
|\ \ \
| * | | diff:add option to ignore blank line changesyuuri2021-05-011-0/+4
| | | |
* | | | Merge pull request #5850 from punkymaniac/comment-formatEdward Thomson2021-05-162-21/+16
|\ \ \ \ | | | | | | | | | | Fix documentation formatting
| * | | | Fix typopunkymaniac2021-04-221-1/+1
| | | | |
| * | | | Uniformise documentation return code separatorpunkymaniac2021-04-221-7/+7
| | | | |
| * | | | Fix documentation formattingpunkymaniac2021-04-221-13/+8
| |/ / / | | | | | | | | | | | | | | | | | | | | The return code description use '-' char as list of return value. But with the generation of the documentation the char '-' create an ambiguous return code value who seem an negative value.
* | | | Merge branch 'zero_oid_in_old'Edward Thomson2021-05-161-0/+3
|\ \ \ \ | |_|/ / |/| | | | | | | Manually merging #5842
| * | | git_reference_create_matching: Treat all-zero OID as "must be absent"David Turner2021-04-201-0/+3
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is pretty useful in avoiding races: I want to create a ref only if it doesn't already exist. I can't check first because of TOCTOU -- by the time I finish the check, someone else might have already created the ref. And I can't take a lock because then I can't do the create, since the create expects to take the lock. The semantics are inspired by git update-ref, which allows an all-zero old value to mean that the ref must not exist.
* | | filter: deprecate git_filter_list_apply_to_dataEdward Thomson2021-05-062-13/+10
| | | | | | | | | | | | | | | Deprecate `git_filter_list_apply_to_data` as it takes user input as a `git_buf`. Users should use `git_filter_list_apply_to_buffer` instead.
* | | filter: introduce git_filter_list_apply_to_bufferEdward Thomson2021-05-061-0/+15
| | | | | | | | | | | | | | | Provide a filter application mechanism that takes a user-provided string and length, instead of a `git_buf`.
* | | filter: remove git_buf sharing in `git_filter_list_apply_to_data`Edward Thomson2021-05-061-12/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The API `git_filter_list_apply_to_data` shares data between its out and in parameters to avoid unnecessarily copying it when there are no filters to apply. However, it does so in a manner that is potentially confusing, leaving both `git_buf`s populated with data. This is risky for end-users who have to know how to deal with this. Instead, we remove this optimization - users who want to avoid unnecessary copies can use the longstanding streaming API or check the filter status before invoking the filters.
* | | filter: deprecate git_filter_list_stream_dataEdward Thomson2021-05-062-3/+29
|/ / | | | | | | | | | | | | | | `git_filter_list_stream_data` takes user input in a `git_buf`. `git_buf` should only be used when libgit2 itself needs to allocate data and returned to a user that they can free when they wish. Replace it with `git_filter_list_stream_buffer` that takes a data buffer and length.
* | Merge pull request #5838 from mjsir911/msirabella/entrycount_typo_fixEdward Thomson2021-04-131-1/+1
|\ \ | |/ |/| Fix diff_entrycount -> diff_num_deltas doc typo
| * Fix diff_entrycount -> diff_num_deltas doc typoMarco Sirabella2021-04-121-1/+1
| | | | | | | | | | This just fixes a typo in the documentation, actual rename change was done in 5f69a31f
View Lorry Controller Status