summaryrefslogtreecommitdiff
path: root/src/pack.c
diff options
context:
space:
mode:
authorEdward Thomson <ethomson@edwardthomson.com>2019-01-17 10:40:13 +0000
committerEdward Thomson <ethomson@edwardthomson.com>2019-01-17 10:54:03 +0000
commitcd350852206481e984f7847a903de8d350ad7bf1 (patch)
tree8d175334bc10172bcd2e28052517771a492ad16d /src/pack.c
parent90046899572f7230ceeab5fef3a909f53f817ba1 (diff)
downloadlibgit2-cd350852206481e984f7847a903de8d350ad7bf1.tar.gz
object_type: GIT_OBJECT_BAD is now GIT_OBJECT_INVALID
We use the term "invalid" to refer to bad or malformed data, eg `GIT_REF_INVALID` and `GIT_EINVALIDSPEC`. Since we're changing the names of the `git_object_t`s in this release, update it to be `GIT_OBJECT_INVALID` instead of `BAD`.
Diffstat (limited to 'src/pack.c')
-rw-r--r--src/pack.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/pack.c b/src/pack.c
index 4e963ecc8..86c8c7256 100644
--- a/src/pack.c
+++ b/src/pack.c
@@ -644,7 +644,7 @@ int git_packfile_unpack(
obj->data = NULL;
obj->len = 0;
- obj->type = GIT_OBJECT_BAD;
+ obj->type = GIT_OBJECT_INVALID;
/* let's point to the right stack */
stack = chain.ptr ? chain.ptr : small_stack;
@@ -726,7 +726,7 @@ int git_packfile_unpack(
base = *obj;
obj->data = NULL;
obj->len = 0;
- obj->type = GIT_OBJECT_BAD;
+ obj->type = GIT_OBJECT_INVALID;
error = git_delta_apply(&obj->data, &obj->len, base.data, base.len, delta.data, delta.len);
obj->type = base_type;