| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Introduce `git_blob_data_is_binary` to examine a blob's data, instead of
the blob itself. A replacement for `git_buf_is_binary`.
|
|
|
|
|
| |
Users may want to validate raw object content; provide them a function
to do so.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Return `GIT_EINVALID` on parse errors so that direct callers of parse
functions can determine when there was a failure to parse the object.
The object parser functions will swallow this error code to prevent it
from propagating down the chain to end-users. (`git_merge` should not
return `GIT_EINVALID` when a commit it tries to look up is not valid,
this would be too vague to be useful.)
The only public function that this affects is
`git_signature_from_buffer`, which is now documented as returning
`GIT_EINVALID` when appropriate.
|
|\
| |
| | |
Minor code cleanups
|
| |
| |
| |
| |
| |
| | |
Instead of using the project-specific `libgit2_SOURCE_DIR` and
`libgit2_BINARY_DIR` variables, use `CMAKE_SOURCE_DIR` and
`CMAKE_BINARY_DIR`.
|
| |
| |
| |
| |
| | |
The filebuf functions should use hashes directly, not indirectly
using the oid functions.
|
| |
| |
| |
| | |
Remove some unnecessary includes from utility code.
|
|\ \
| |/
|/| |
Fix repo init when template dir is non-existent
|
| | |
|
| |
| |
| |
| |
| | |
This mimics the behaviour of git which just prints a
warning and continues with the repo initialisation.
|
| | |
|
| |
| |
| |
| | |
Instead of `git__date`, just use `git_date`.
|
| |
| |
| |
| |
| | |
`git_tag_name_is_valid` needs to set validity to 0 when it
short-circuits.
|
| | |
|
| |
| |
| |
| |
| | |
The select hashes module selects the hash; the CMakeLists.txt selects
the files to implement it.
|
| |
| |
| |
| |
| | |
Update the global variables `LIBGIT2_OBJECTS` to
`LIBGIT2_DEPENDENCY_OBJECTS` for clarity and consistency.
|
|\ \
| | |
| | |
| | | |
lhchavez/drop-volatile-qualifier-in-atomic-exchange
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When building under gcc 11, there is a warning about an incompatible pointer
type, since
[`__atomic_exchange`](https://gcc.gnu.org/onlinedocs/gcc/_005f_005fatomic-Builtins.html)
does not take `volatile` pointers:
```
In file included from ../src/common.h:81,
from ../src/transports/winhttp.c:8:
../src/thread-utils.h: In function ‘git___swap’:
../src/thread-utils.h:168:9: warning: argument 3 of ‘__atomic_exchange’ discards ‘volatile’ qualifier [-Wincompatible-pointer-types]
168 | __atomic_exchange(ptr, &newval, &foundval, __ATOMIC_SEQ_CST);
| ^~~~~~~~~~~~~~~~~
```
This change drops the `volatile` qualifier so that the pointer type matches
what `__atomic_exchange` expects.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When building under gcc 11, there is a warning about a misaligned guard clause
because there were mixed spaces and tabs:
```
[128/634] Building C object src/CMakeFiles/git2internal.dir/threadstate.c.o
../src/threadstate.c: In function ‘threadstate_dispose’:
../src/threadstate.c:39:5: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
39 | if (threadstate->error_t.message != git_str__initstr)
| ^~
../src/threadstate.c:41:9: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
41 | threadstate->error_t.message = NULL;
| ^~~~~~~~~~~
../src/threadstate.c: At top level:
```
This change indents the code with tabs for consistency with the rest of the
code, which makes the warning go away.
|
| |
| |
| |
| |
| | |
We should enforce declarations throughout the code-base, including
examples, fuzzers and tests, not just in the `src` tree.
|
|\ \
| | |
| | | |
cmake refactorings
|
| | |
| | |
| | |
| | | |
Move zlib selection into its own cmake module.
|
| | |
| | |
| | |
| | | |
Move WinHTTP selection into its own cmake module.
|
| | |
| | |
| | |
| | | |
Move SSH selection into its own cmake module.
|
| | |
| | |
| | |
| | | |
Move regex selection into its own cmake module.
|
| | |
| | |
| | |
| | | |
Move http_parser selection into its own cmake module.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
There's no need to add the deprecation at the top-level. Our tests add
deprecation explicitly.
|
| | |
| | |
| | |
| | |
| | | |
WinHTTP can now be disabled with `USE_WINHTTP=OFF` instead of
`WINHTTP=OFF` to better support the other cmake semantics.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Threading can now be disabled with `USE_THREADS=OFF` instead of
`THREADSAFE=OFF` to better support the other cmake semantics.
Nanosecond support is the default _if_ we can detect it. This should be
our default always - like threads - and people can opt out explicitly.
|
|/ / |
|
|\ \
| | |
| | | |
path: refactor utility path functions
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Teach `git_path_is_valid` to respect `core.longpaths`. Add helper
methods to validate length and set the error message appropriately.
|
| | |
| | |
| | |
| | |
| | | |
Add a `git_str` based validity check; the existing `git_path_is_valid`
defers to it.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Provide a mechanism for users to limit the number of characters that are
examined; `git_fs_path_str_is_valid` and friends will only examine up to
`str->size` bytes.
`git_fs_path_is_valid` delegates to these new functions by passing
`SIZE_MAX` (instead of doing a `strlen`), which is a sentinel value
meaning "look for a NUL terminator".
|
| | |
| | |
| | |
| | |
| | | |
Since we're returning a boolean about validation, the name is more
properly "is valid".
|
| | |
| | |
| | |
| | |
| | | |
Since we're returning a boolean about validation, the name is more
properly "is valid".
|
| |/
| |
| |
| |
| |
| | |
Introduce `git_fs_path`, which operates on generic filesystem paths.
`git_path` will be kept for only git-specific path functionality (for
example, checking for `.git` in a path).
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Looking up a non-existent object currently always invokes
`git_odb_refresh`. If looking up a large batch of objects, many of which
may legitimately not exist, this will repeatedly refresh the ODB to no
avail.
Add a `git_odb_exists_ext` that accepts flags controlling the ODB
lookup, and add a flag to suppress the refresh. This allows the user to
control if and when they refresh (for instance, refreshing once before
starting the batch).
|
|
|
|
|
| |
Ensure that we always use lowercase function names, and that we do not
have spaces preceding open parentheses, for consistency.
|
|
|
|
| |
There's no need to make tracing opt-in; it should always be included.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
libgit2 has two distinct requirements that were previously solved by
`git_buf`. We require:
1. A general purpose string class that provides a number of utility APIs
for manipulating data (eg, concatenating, truncating, etc).
2. A structure that we can use to return strings to callers that they
can take ownership of.
By using a single class (`git_buf`) for both of these purposes, we have
confused the API to the point that refactorings are difficult and
reasoning about correctness is also difficult.
Move the utility class `git_buf` to be called `git_str`: this represents
its general purpose, as an internal string buffer class. The name also
is an homage to Junio Hamano ("gitstr").
The public API remains `git_buf`, and has a much smaller footprint. It
is generally only used as an "out" param with strict requirements that
follow the documentation. (Exceptions exist for some legacy APIs to
avoid breaking callers unnecessarily.)
Utility functions exist to convert a user-specified `git_buf` to a
`git_str` so that we can call internal functions, then converting it
back again.
|
|\
| |
| | |
hash: separate hashes and git_oid
|