summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
* | | | | | | | Limit ITimer usage to AmigaOS4Peter Pettersson2021-07-061-1/+1
| |_|/ / / / / |/| | | | | |
* | | | | | | Merge pull request #5915 from novalis/executableEdward Thomson2021-07-021-1/+1
|\ \ \ \ \ \ \ | |_|_|_|_|_|/ |/| | | | | | Consider files executable only if the user can execute them
| * | | | | | Consider files executable only if the user can execute themDavid Turner2021-06-161-1/+1
| | |/ / / / | |/| | | | | | | | | | | | | | | | This is what git.git does, so we should follow suit.
* | | | | | define WINHTTP_NO_CLIENT_CERT_CONTEXT if neededJacques Germishuys2021-06-261-0/+4
|/ / / / /
* | | | | Tolerate readlink size less than st_sizeDavid Tolnay2021-05-301-3/+4
|/ / / /
* | | | Merge branch 'pr/5853'Edward Thomson2021-05-191-0/+3
|\ \ \ \
| * | | | diff:add option to ignore blank line changesyuuri2021-05-011-0/+3
| | | | |
* | | | | tests: exit with error on win32 leakcheckEdward Thomson2021-05-182-0/+7
| | | | |
* | | | | Merge pull request #5852 from implausible/httpclient/skip-entire-bodyEdward Thomson2021-05-161-4/+9
|\ \ \ \ \ | | | | | | | | | | | | Fix issues with Proxy Authentication after httpclient refactor
| * | | | | httpclient: no proxy creds in requests if proxy is CONNECT typeTyler Ang-Wanek2021-05-121-3/+8
| | | | | |
| * | | | | httpclient: git_http_client_skip_body should drain socket of bodyTyler Ang-Wanek2021-05-121-1/+1
| |/ / / /
* | | | | Merge branch 'zero_oid_in_old'Edward Thomson2021-05-161-1/+4
|\ \ \ \ \ | |_|_|/ / |/| | | | | | | | | Manually merging #5842
| * | | | git_reference_create_matching: Treat all-zero OID as "must be absent"David Turner2021-04-201-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | | diff: Fix bug in git_diff_find_similar.Kartikaya Gupta2021-05-121-2/+2
| |_|_|/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When a split src gets turned into a rename, it should also lose the IS_RENAME_TARGET flag, so that it doesn't get processed in a subsequent iteration as a rename target. Doing so can cause an assertion failure because it no longer has the SPLIT flag. Fixes #5811.
* | | | Merge pull request #5860 from libgit2/ethomson/buf_textEdward Thomson2021-05-1114-477/+418
|\ \ \ \ | | | | | | | | | | buf: remove unnecessary buf_text namespace
| * | | | buf: bom enum is in the buf namespaceEdward Thomson2021-05-114-22/+22
| | | | | | | | | | | | | | | | | | | | | | | | | Instead of a `git_bom_t` that a `git_buf` function returns, let's keep it `git_buf_bom_t`.
| * | | | buf: remove internal `git_buf_text` namespaceEdward Thomson2021-05-1114-473/+414
| | | | | | | | | | | | | | | | | | | | | | | | | The `git_buf_text` namespace is unnecessary and strange. Remove it, just keep the functions prefixed with `git_buf`.
* | | | | filter: internal git_buf filter handling functionEdward Thomson2021-05-065-8/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Introduce `git_filter_list__convert_buf` which behaves like the old implementation of `git_filter_list__apply_data`, where it might move the input data buffer over into the output data buffer space for efficiency. This new implementation will do so in a more predictible way, always freeing the given input buffer (either moving it to the output buffer or filtering it into the output buffer first). Convert internal users to it.
* | | | | filter: deprecate git_filter_list_apply_to_dataEdward Thomson2021-05-061-11/+11
| | | | | | | | | | | | | | | | | | | | | | | | | 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-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | 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/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-061-10/+24
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | `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 #5858 from libgit2/ethomson/memleaksEdward Thomson2021-05-061-0/+1
|\ \ \ \ | | | | | | | | | | test: clean up memory leaks
| * | | | test: clean up memory leaksEdward Thomson2021-05-061-0/+1
| | | | |
* | | | | path: bump most Win32 unicode buffer sizes from MAX_PATH to GIT_PATH_MAXIan Hattendorf2021-05-052-19/+28
|/ / / /
* | | | Merge pull request #5823 from libgit2/ethomson/path_validationEdward Thomson2021-05-0231-300/+612
|\ \ \ \ | |_|/ / |/| | | Working directory path validation
| * | | repo: validate repository pathsEdward Thomson2021-04-281-7/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Ensure that a repository's path (at initialization or open time) is valid. On Windows systems, this means that the longest known path beneath the repository will fit within MAX_PATH: this is a lock file for a loose object within the repository itself. Other paths, like a very long loose reference, may fail to be opened after the repository is opened. These variable length paths will be checked when they are accessed themselves. This new functionality is done at open to prevent needlessly checking every file in the gitdir (eg, `MERGE_HEAD`) for its length when we could instead check once at repository open time.
| * | | repo: factor the commondir detectionEdward Thomson2021-04-281-28/+41
| | | |
| * | | refs: ensure loose refs adhere to path validationEdward Thomson2021-04-281-30/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | On Windows, we need to enforce MAX_PATH for loose references and their reflogs. Ensure that any path - including the lock file - would fit within the 260 character maximum. We do not honor core.longpaths for loose reference files or reflogs. core.longpaths only applies to paths in the working directory.
| * | | path: don't join paths in git_path_find_dirEdward Thomson2021-04-283-11/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Let `git_path_find_dir` simply take a `git_buf` that contains a directory or a file, instead of trying to both join a path AND then deal with prettifying it or its basename. This allows consumers to join paths themselves (and apply any necessary rules - like fitting within MAX_PATH).
| * | | worktree: validate worktree pathsEdward Thomson2021-04-281-2/+5
| | | | | | | | | | | | | | | | | | | | Worktree paths need to fix within MAX_PATH always, regardless of `core.longpaths` setting.
| * | | submodule: validate path lengthsEdward Thomson2021-04-281-27/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Validate that working directory paths honor `core.longpaths` where appropriate. Paths to the submodule gitdirs must always honor the operating system length restrictions; `core.longpaths` does not affect gitdir paths.
| * | | iterator: validate workdir pathsEdward Thomson2021-04-281-4/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Supply the repository for the filesystem and workdir iterators - for workdir iterators, this is non-null and we can lookup the core.longpaths configuration option. (For regular filesystem iterators, this is NULL, so core.longpaths does not apply.)
| * | | ignore: validate workdir paths for ignore filesEdward Thomson2021-04-281-7/+10
| | | |
| * | | attr: validate workdir paths for attribute filesEdward Thomson2021-04-286-13/+27
| | | | | | | | | | | | | | | | | | | | | | | | We should allow attribute files - inside working directories - to have names longer than MAX_PATH when core.longpaths is set. `git_attr_path__init` takes a repository to validate the path with.
| * | | repository: validate workdir path lengthsEdward Thomson2021-04-281-3/+3
| | | |
| * | | workdir: validate working directory entry path lengthEdward Thomson2021-04-281-1/+3
| | | |
| * | | diff: use git_repository_workdir_pathEdward Thomson2021-04-283-6/+4
| | | | | | | | | | | | | | | | | | | | | | | | The new git_repository_workdir_path function does error checking on working directory inputs on Windows; use it to construct paths within working directories.
| * | | use git_repository_workdir_path to generate pathsEdward Thomson2021-04-284-9/+8
| | | | | | | | | | | | | | | | | | | | Use `git_repository_workdir_path` to generate workdir paths since it will validate the length.
| * | | checkout: validate path lengthEdward Thomson2021-04-281-5/+22
| | | | | | | | | | | | | | | | | | | | Ensure that we are validating working directory paths before we try to write to them.
| * | | checkout: use target path; don't assume workdirEdward Thomson2021-04-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | We're not necessarily checking out into the working directory. We could be checking out into an arbitrary location. Ensure that when we are writing conflict data that we do it in the checkout target.
| * | | repo: introduce git_repository_workdir_pathEdward Thomson2021-04-282-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Add a simple accessor for workdir paths to get an absolute on-disk path given a repository and a relative path within it. This is useful to avoid copy-pasta `git_buf_joinpath` and to ensure that we validate working directory paths while honoring `core.longpaths` settings.
| * | | apply: ensure we validate pathsEdward Thomson2021-04-281-2/+2
| | | | | | | | | | | | | | | | | | | | There was no test ensuring that we validate `.git` paths. We do, but let's add a test to make sure that we never regress this.
| * | | path: introduce ondisk and workdir path validationEdward Thomson2021-04-284-0/+114
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Introduce `git_path_validate_filesystem` which validates (absolute) on-disk paths and `git_path_validate_workdir` to perform validations on (absolute) working directory paths. These functions are useful as there may be system limitations on on-disk paths, particularly on Windows (for example, enforcing MAX_PATH). For working directory paths, these limitations may be per-repository, based on the `core.longpaths` configuration setting.
| * | | path: git_path_isvalid -> git_path_validateEdward Thomson2021-04-147-11/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | If we want to validate more and different types of paths, the name `git_path_validate` makes that easier and more expressive. We can add, for example, `git_path_validate_foo` while the current name makes that less ergonomic.
| * | | utf8: introduce git_utf8_char_lengthEdward Thomson2021-04-142-0/+38
| | | | | | | | | | | | | | | | | | | | Introduce a function to determine the number of Unicode characters in a given UTF-8 string.
| * | | utf8: refactor utf8 functionsEdward Thomson2021-04-147-143/+169
| | |/ | |/| | | | | | | | | | | | | | | | | | | Move the utf8 functions into a proper namespace `git_utf8` instead of being in the namespaceless `git__` function group. Update them to have out-params first and use `char *` instead of `uint8_t *` to match our API treating strings as `char *` (even if they truly contain `uchar`s inside).
* | | src: fix typos in header filesTobias Nießen2021-04-182-2/+2
| |/ |/|
* | Merge pull request #5834 from libgit2/cmn/repo-no-passthroughEdward Thomson2021-04-131-11/+9
|\ \ | | | | | | repo: remove an inappropriate use of PASSTHROUGH
| * | repo: remove an inappropriate use of PASSTHROUGHcmn/repo-no-passthroughCarlos Martín Nieto2021-04-111-11/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This error code is for callbacks where we should act as though the callback was not set. This is not something that makes sense for a `_foreach` and checking for that error message to bubble up mostly is happenstance precisely because this is not an error code we expect in the callback. As part of removing this, let's also remove a use of foreach as we can open-code this check.
View Lorry Controller Status