Skip to content

More git_obj to git_object updates#4940

Merged
ethomson merged 3 commits intomasterfrom
ethomson/git_obj
Jan 19, 2019
Merged

More git_obj to git_object updates#4940
ethomson merged 3 commits intomasterfrom
ethomson/git_obj

Conversation

@ethomson
Copy link
Copy Markdown
Member

Some further tweaks on moving to git_object. 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_ts in this release, update it to be GIT_OBJECT_INVALID instead of BAD.

Per @tiennou's note in #4917, I've also updated the compatibility declarations to be static const ints instead of #defines, allowing us to mark them as deprecated using GIT_DEPRECATED.

Doing so illustrated some places where we were continuing to use the old names internally; they've also been updated.

Mark old object type values as `static const` so that we can mark them
as deprecated with the `GIT_DEPRECATED` macro.
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`.
Update some missed types that were continuing to use the old `GIT_OBJ`
names.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant