- 09 Mar, 2016 1 commit
-
-
The old implementation had two issues: 1. OIDs that were too short as to be ambiguous were not being handled properly. 2. If the last OID to expand in the array was missing from the ODB, we would leak a `GIT_ENOTFOUND` error code from the function.
Vicent Marti committed
-
- 08 Mar, 2016 2 commits
-
-
Take (and write to) an array of a struct, `git_odb_expand_id`.
Edward Thomson committed -
Edward Thomson committed
-
- 07 Mar, 2016 1 commit
-
-
Query the object database for multiple objects at a time, given their object ID (which may be abbreviated) and optional type.
Edward Thomson committed
-
- 01 Jul, 2014 1 commit
-
-
Edward Thomson committed
-
- 04 Mar, 2014 1 commit
-
-
Russell Belfer committed
-
- 14 Nov, 2013 1 commit
-
-
Ben Straub committed
-
- 12 Aug, 2013 1 commit
-
-
By the time we recognise this as an ambiguous id, the object's data has been loaded into memory. Free it when returning EABMIGUOUS.
Carlos Martín Nieto committed
-
- 08 Aug, 2013 1 commit
-
-
This is based on 24634c6f. This also corrects an issue with error codes being mixed up with the number of found objects.
Brodie Rao committed
-
- 06 Aug, 2013 1 commit
-
-
The test coverage for ambiguous OIDs was pretty thin. This adds a bunch of new objects both in packs, across packs, and loose that match to 8 characters so that we can test various cases of ambiguous lookups.
Russell Belfer committed
-
- 23 Nov, 2012 1 commit
-
-
Without this change, any failed assertion in the second (or a later) test inside a test suite has a chance of double deleting memory, resulting in a heap corruption. See #1096 for details. This leaves alone the test cases where we "just" use cl_git_sandbox_init() and cl_git_sandbox_cleanup(). These methods already take good care to not double delete a repository. Fixes #1096
Sascha Cunz committed
-
- 16 May, 2012 1 commit
-
-
Vicent Martí committed
-
- 12 May, 2012 1 commit
-
-
Han-Wen Nienhuys committed
-