- 27 Aug, 2021 1 commit
-
-
This change adds the git_midx_writer_* functions to allow to write and create `multi-pack-index` files from `.idx`/`.pack` files. Part of: #5399
lhchavez committed
-
- 09 Aug, 2021 3 commits
- 08 Aug, 2021 1 commit
-
-
Like on Windows ':' is used for volume names in absolute paths.
Peter Pettersson committed
-
- 30 Jul, 2021 2 commits
-
-
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.
Tony De La Nuez committed -
Document `GIT_STATUS_OPT_INCLUDE_UNREADABLE`, and some minor cleanups.
Edward Thomson committed
-
- 27 Jul, 2021 2 commits
-
-
len, array -> array, len
lhchavez committed -
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
lhchavez committed
-
- 22 Jul, 2021 4 commits
-
-
Provide a mechanism to filter using attribute data from a specific commit (making use of `GIT_ATTR_CHECK_INCLUDE_COMMIT`).
Edward Thomson committed -
Introduce `GIT_ATTR_CHECK_INCLUDE_COMMIT`, which like 4fd5748c allows attribute information to be read from files in the repository. 4fd5748c always reads the information from HEAD, while `GIT_ATTR_CHECK_INCLUDE_COMMIT` allows users to provide the commit to read the attributes from.
Edward Thomson committed -
Allow filter users to provide an options structure instead of simply flags. This allows for future growth for filter options.
Edward Thomson committed -
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.
Edward Thomson committed
-
- 06 Jul, 2021 5 commits
-
-
punkymaniac committed
-
punkymaniac committed
-
punkymaniac committed
-
punkymaniac committed
-
punkymaniac committed
-
- 15 Jun, 2021 2 commits
-
-
Dmitry Lobanov committed
-
Waleed Khan committed
-
- 13 Jun, 2021 1 commit
-
-
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`.
Waleed Khan committed
-
- 02 Jun, 2021 4 commits
-
-
punkymaniac committed
-
punkymaniac committed
-
punkymaniac committed
-
punkymaniac committed
-
- 01 Jun, 2021 1 commit
-
-
Dmitry Lobanov committed
-
- 27 May, 2021 1 commit
-
-
Etienne Samson committed
-
- 26 May, 2021 1 commit
-
-
Dmitry Lobanov committed
-
- 16 May, 2021 1 commit
-
-
Dmitry Lobanov committed
-
- 12 May, 2021 1 commit
-
-
Dmitry Lobanov committed
-
- 06 May, 2021 4 commits
-
-
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.
Edward Thomson committed -
Provide a filter application mechanism that takes a user-provided string and length, instead of a `git_buf`.
Edward Thomson committed -
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.
Edward Thomson committed -
`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.
Edward Thomson committed
-
- 01 May, 2021 1 commit
-
-
yuuri committed
-
- 22 Apr, 2021 3 commits
-
-
punkymaniac committed
-
punkymaniac committed
-
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.
punkymaniac committed
-
- 20 Apr, 2021 1 commit
-
-
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.
David Turner committed
-
- 13 Apr, 2021 1 commit
-
-
This just fixes a typo in the documentation, actual rename change was done in 5f69a31f
Marco Sirabella committed
-