summaryrefslogtreecommitdiff
path: root/include/git2
Commit message (Collapse)AuthorAgeFilesLines
* Update documentation for git_blob_filter_optionsJosh Stockin2021-01-051-1/+2
| | | | Adds info about initializing options with git_blob_filter_options_init
* blob: add git_blob_filter_options_initEdward Thomson2021-01-051-0/+12
| | | | | | The `git_blob_filter_options_init` function should be included, to allow callers in FFI environments to let us initialize an options structure for them.
* Fix documentation for git_blob_filter_optionsJosh Stockin2021-01-041-1/+1
|
* Move doc comment about `GIT_BLOB_FILTER_OPTIONS_VERSION`Josh Stockin2021-01-041-1/+3
| | | | | | | | | | Removes doc comment on `git_blob_filter_options.version`, moves information to `git_blob_filter_options` doc comment to remain consistent with other options structures' documentation. `git_blob_filter_options_init` still needed; should be added in another commit/PR (it's out of the scope of this PR, #5759), update this documentation again.
* Add documentation for git_blob_filter_options.versionJosh Stockin2021-01-031-0/+1
| | | | Resolves #5756
* Add support for additional hostkey types.Miguel Arroz2020-12-211-0/+8
| | | | Specifically: ECDSA_256, ECDSA_384, ECDSA_521 and ED25519.
* Also add the raw hostkey to `git_cert_hostkey`lhchavez2020-11-271-5/+33
| | | | | `git_cert_x509` has the raw encoded certificate. Let's do the same for the SSH certificate for symmetry.
* blob: use GIT_ASSERTEdward Thomson2020-11-251-1/+1
|
* Add git_tag_name_is_validSven Strickroth2020-10-251-0/+12
| | | | Signed-off-by: Sven Strickroth <email@cs-ware.de>
* Add git_branch_name_is_validSven Strickroth2020-10-251-0/+12
| | | | Signed-off-by: Sven Strickroth <email@cs-ware.de>
* remote: deprecate git_remote_is_valid_nameEdward Thomson2020-10-252-8/+21
|
* refs: introduce git_remote_name_is_validEdward Thomson2020-10-251-0/+9
| | | | | | | | Provide a function that can check remote name validity but can also signal when an error occurs. Use the name "name_is_valid", which is more suggestive of checking a given name, rather than "is_valid_name", which suggests that the function checks the validity of the current remote's name.
* refs: deprecate git_reference_is_valid_nameEdward Thomson2020-10-252-19/+21
|
* refs: introduce git_reference_name_is_validEdward Thomson2020-10-251-0/+17
| | | | | | | | Provide a function that can check reference name validity but can also signal when an error occurs. Use the name "name_is_valid", which is more suggestive of checking a given name, rather than "is_valid_name", which suggests that the function checks the validity of the current reference's name.
* Release v1.1ethomson/v1.1Edward Thomson2020-10-121-3/+3
|
* Fixed typo in commentIkko Ashimine2020-10-041-1/+1
| | | occured -> occurred
* Fix deprecation links inside of documentation not workingSven Strickroth2020-09-101-1/+5
| | | | Signed-off-by: Sven Strickroth <email@cs-ware.de>
* docs: fix typoSven2020-08-181-1/+1
|
* Review feedbacklhchavez2020-06-261-1/+1
| | | | | | | | | | * Change the default of the file limit to 0 (unlimited). * Changed the heuristic to close files to be the file that contains the least-recently-used window such that the window is the most-recently-used in the file, and the file does not have in-use windows. * Parameterized the filelimit test to check for a limit of 1 and 100 open windows.
* mwindow: set limit on number of open fileslhchavez2020-06-211-3/+15
| | | | | | | | | | | | | | | | | | There are some cases in which repositories accrue a large number of packfiles. The existing mwindow limit applies only to the total size of mmap'd files, not on their number. This leads to a situation in which having lots of small packfiles could exhaust the allowed number of open files, particularly on macOS, where the default ulimit is very low (256). This change adds a new configuration parameter (GIT_OPT_SET_MWINDOW_FILE_LIMIT) that sets the maximum number of open packfiles, with a default of 128. This is low enough so that even macOS users should not hit it during normal use. Based on PR #5386, originally written by @josharian. Fixes: #2758
* Merge pull request #5419 from lhchavez/fix-git_index_add_from_buffer-docsPatrick Steinhardt2020-06-171-2/+1
|\ | | | | index: Update the documentation for git_index_add_from_buffer()
| * index: Update the documentation for git_index_add_from_buffer()lhchavez2020-02-231-2/+1
| | | | | | | | | | This change makes the docs reflect reality. The id and size were never updated in the entry!
* | Merge pull request #5532 from joshtriplett/pack-default-pathEdward Thomson2020-06-021-1/+1
|\ \ | | | | | | git_packbuilder_write: Allow setting path to NULL to use the default path
| * | git_packbuilder_write: Allow setting path to NULL to use the default pathJosh Triplett2020-05-231-1/+1
| | | | | | | | | | | | | | | | | | If given a NULL path, write to the object path of the repository. Add tests for the new behavior.
* | | strarray: deprecate git_strarray_copyEdward Thomson2020-06-011-0/+12
| | | | | | | | | | | | | | | | | | We should not be in the business of copying strings around for users. We either return a strarray that can be freed, or we take one (and do not mutate it).
* | | strarray: we should `dispose` instead of `free`Edward Thomson2020-06-012-10/+30
|/ / | | | | | | | | | | We _dispose_ the contents of objects; we _free_ objects (and their contents). Update `git_strarray_free` to be `git_strarray_dispose`. `git_strarray_free` remains as a deprecated proxy function.
* | Introduce GIT_ASSERT macrosEdward Thomson2020-05-111-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | Provide macros to replace usages of `assert`. A true `assert` is punishing as a library. Instead we should do our best to not crash. GIT_ASSERT_ARG(x) will now assert that the given argument complies to some format and sets an error message and returns `-1` if it does not. GIT_ASSERT(x) is for internal usage, and available as an internal consistency check. It will set an error message and return `-1` in the event of failure.
* | blame: add option to ignore whitespace changesCarl Schwan2020-04-141-0/+2
| |
* | version.h: bump version to v1.0.0Patrick Steinhardt2020-03-281-4/+4
| |
* | Merge pull request #5464 from pks-t/pks/refdb-backend-docsPatrick Steinhardt2020-03-261-2/+109
|\ \ | | | | | | refdb_backend: improve callback documentation
| * | refdb_backend: improve callback documentationPatrick Steinhardt2020-03-261-2/+109
| | | | | | | | | | | | | | | | | | | | | The callbacks are currently sparsely documented, making it really hard to implement a new backend without taking a look at the existing refdb_fs backend. Add documentation to make this task hopefully easier to achieve.
* | | credentials: provide backcompat for opaque structsethomson/cred_deprecationEdward Thomson2020-03-261-0/+7
|/ / | | | | | | | | | | The credential structures are now opaque and defined in `sys/credential.h`. However, we should continue to provide them for backward compatibility, unless `GIT_DEPRECATED_HARD` is set.
* | repository: improve commondir docsJosh Bleecher Snyder2020-03-071-4/+5
|/ | | | Fixes #5428
* version: update the version number to v0.99Edward Thomson2020-02-191-3/+3
| | | | | | This commit also switches our SOVERSION to be "$MAJOR.$MINOR" instead of "$MINOR", only. This is in preparation of v1.0, where the previous scheme would've stopped working in an obvious way.
* Merge pull request #5336 from libgit2/ethomson/credtypePatrick Steinhardt2020-01-3010-183/+289
|\ | | | | cred: change enum to git_credential_t and GIT_CREDENTIAL_*
| * credential: change git_cred to git_credentialethomson/credtypeEdward Thomson2020-01-2610-183/+289
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We avoid abbreviations where possible; rename git_cred to git_credential. In addition, we have standardized on a trailing `_t` for enum types, instead of using "type" in the name. So `git_credtype_t` has become `git_credential_t` and its members have become `GIT_CREDENTIAL` instead of `GIT_CREDTYPE`. Finally, the source and header files have been renamed to `credential` instead of `cred`. Keep previous name and values as deprecated, and include the new header files from the previous ones.
* | git_libgit2_version: return an intethomson/no_voidEdward Thomson2020-01-241-1/+2
| | | | | | | | | | Stop returning a void for functions, future-proofing them to allow them to fail.
* | error functions: return an intEdward Thomson2020-01-241-1/+2
| | | | | | | | | | Stop returning a void for functions, future-proofing them to allow them to fail.
* | revwalk functions: return an intEdward Thomson2020-01-241-3/+7
| | | | | | | | | | Stop returning a void for functions, future-proofing them to allow them to fail.
* | mempack functions: return an intEdward Thomson2020-01-241-1/+2
| | | | | | | | | | Stop returning a void for functions, future-proofing them to allow them to fail.
* | repository functions: return an intEdward Thomson2020-01-241-5/+12
| | | | | | | | | | Stop returning a void for functions, future-proofing them to allow them to fail.
* | index functions: return an intEdward Thomson2020-01-241-2/+4
| | | | | | | | | | Stop returning a void for functions, future-proofing them to allow them to fail.
* | remote functions: return an intEdward Thomson2020-01-241-2/+4
| | | | | | | | | | Stop returning a void for functions, future-proofing them to allow them to fail.
* | tree functions: return an intEdward Thomson2020-01-241-2/+4
| | | | | | | | | | Stop returning a void for functions, future-proofing them to allow them to fail.
* | oid functions: return an intEdward Thomson2020-01-241-5/+10
| | | | | | | | | | Stop returning a void for functions, future-proofing them to allow them to fail.
* | git_attr_cache_flush: return an intEdward Thomson2020-01-241-1/+4
|/ | | | | Stop returning a void for functions, future-proofing them to allow them to fail.
* http: introduce GIT_ERROR_HTTPethomson/gssapiEdward Thomson2020-01-241-1/+2
| | | | | Disambiguate between general network problems and HTTP problems in error codes.
* httpclient: support expect/continueEdward Thomson2020-01-241-1/+7
| | | | | | | | | | | | | Allow users to opt-in to expect/continue handling when sending a POST and we're authenticated with a "connection-based" authentication mechanism like NTLM or Negotiate. If the response is a 100, return to the caller (to allow them to post their body). If the response is *not* a 100, buffer the response for the caller. HTTP expect/continue is generally safe, but some legacy servers have not implemented it correctly. Require it to be opt-in.
* merge: Return non-const git_repository from git_merge_driver_source_repo ↵Laurence McGlashan2020-01-151-1/+1
| | | | accessor.
* Correct typo in name of referenced parameterRemy Suen2020-01-021-1/+1
| | | Signed-off-by: Remy Suen <remy.suen@gmail.com>
View Lorry Controller Status