- 12 Feb, 2023 8 commits
-
-
This is much of the plumbing for the object database to support SHA256, and for objects to be able to parse SHA256 versions of themselves.
Edward Thomson committed -
Edward Thomson committed
-
Teach the packfile machinery to cope with SHA256.
Edward Thomson committed -
In clar, an underscore is meaningful; avoid using it incorrectly / unnecessarily.
Edward Thomson committed -
This is a conversion of the testrepo.git to SHA256 support.
Edward Thomson committed -
Edward Thomson committed
-
Ensure that we maintain the `core.repositoryFormatVersion` value instead of always overwriting it with the default.
Edward Thomson committed -
Teach the repository about the `objectformat` extension, supporting `sha1` always and `sha256` when the experimental sha256 support is active.
Edward Thomson committed
-
- 09 Feb, 2023 1 commit
-
-
Edward Thomson committed
-
- 25 Jan, 2023 3 commits
-
-
Abstract time counter for tests; use gettimeofday on Unix and GetTickCount on Windows.
Edward Thomson committed -
Edward Thomson committed
-
Update to the latest main version of clar, which includes improved xml summary output.
Edward Thomson committed
-
- 25 Nov, 2022 1 commit
-
-
Verify that trying to update submodule which has been configured but not added does return an error. Issue #6433: git_submodule_update fails to update configured but missing submodule
tagesuhu committed
-
- 19 Nov, 2022 1 commit
-
-
Signed-off-by: Sven Strickroth <email@cs-ware.de>
Sven Strickroth committed
-
- 04 Nov, 2022 1 commit
-
-
We're currently running it as part of the online suite but that doesn't have any setup for ssh so we won't find the GitHub keys we set up during the test. It doesn't need the private key setup as we just want to make sure we see some auth request from the server, but with the addition of hostkey checking we're now seeing it fail when we skip these tests.
Carlos Martín Nieto committed
-
- 03 Nov, 2022 1 commit
-
-
It is expensive to compute the sha1 of the entire commit-graph file each time we open it. Git only does this if it is re-writing the file. This patch will only verify the checksum when calling the external API git_commit_graph_open(), which explicitly says it opens and verifies the commit graph in the documentation. For internal library calls, we call git_commit_graph_get_file(), which mmaps the commit-graph file in read-only mode. Therefore it is safe to skip the validation check there. Tests were added to check that the validation works in the happy path, and prevents us from opening the file when validation fails. (Note from Derrick Stolee: This patch was applied internally at GitHub after we recognized the performance impact it had during an upgrade of libgit2. The original author left the company before we remembered to send it upstream.) Signed-off-by: Derrick Stolee <derrickstolee@github.com>
Colin Stolley committed
-
- 01 Oct, 2022 1 commit
-
-
Kevin Saul committed
-
- 19 Sep, 2022 3 commits
-
-
Actually `cl_skip` the sha256 tests when we're not compiled for sha256, instead of passing them.
Edward Thomson committed -
Test that we can successfully clone a repository that is namespace scoped on the remote and does not advertise a HEAD. To do this, we must specify the branch to checkout.
Edward Thomson committed -
Test that we can successfully clone a repository that is namespace scoped to a bare repository locally. We need not specify a checkout branch in this case (obviously, since we do not check anything out in a bare clone).
Edward Thomson committed
-
- 06 Sep, 2022 1 commit
-
-
Laurence McGlashan committed
-
- 31 Aug, 2022 1 commit
-
-
Miguel Arroz committed
-
- 22 Jul, 2022 1 commit
-
-
Kevin Saul committed
-
- 20 Jul, 2022 1 commit
-
-
I want to push a commit by OID to a remote branch. Currently, push parses the refspecs such that the source must be the name of a ref (it uses git_reference_name_to_id to resolve it). This commit changes it so push uses git_revparse_single to resolve the source of the refspec. This allows for OIDs or other revs (e.g. `HEAD~2`) to be pushed.
Sven Over committed
-
- 15 Jul, 2022 1 commit
-
-
Peter Pettersson committed
-
- 14 Jul, 2022 2 commits
-
-
The experimental function signature is only available when `GIT_EXPERIMENTAL_SHA256` is enabled.
Edward Thomson committed -
Edward Thomson committed
-
- 11 Jul, 2022 6 commits
- 09 Jul, 2022 1 commit
-
-
Pack files v3 are introduced in the SHA256 hash transition document https://github.com/git/git/blob/master/Documentation/technical/hash-function-transition.txt Obviously we do not support these yet. Stop pretending that we do.
Edward Thomson committed
-
- 07 Jul, 2022 4 commits
-
-
Allow users in the administrator group to use git configs that are owned by administrators.
Edward Thomson committed -
The file ownership concepts can reflect the actual file ownership, they are not necessarily limited to mocking the interface. Rename them so that they can be more broadly applicable.
Edward Thomson committed -
Ensure that we test opening a bare repository with odd permissions.
Edward Thomson committed -
This reverts commit cdff2f02. This change erroneously allowed system users to own a worktree; this should only be allowed when the current user is in the Administrator group on Windows as well.
Edward Thomson committed
-
- 20 Jun, 2022 2 commits
-
-
libgit2 can be built with optional, experimental sha256 support. This allows consumers to begin testing and providing feedback for our sha256 support while we continue to develop it, and allows us to make API breaking changes while we iterate on a final sha256 implementation. The results will be `git2-experimental.dll` and installed as `git2-experimental.h` to avoid confusion with a production libgit2.
Edward Thomson committed -
Teach the loose object database how to cope with SHA256 objects.
Edward Thomson committed
-