To date, we've generally mirrored libgit2 support only when we need that specific feature. This ensures that the API sees real-world use, avoids bit rot, and reduces the number of places we have to update due to libgit2 changes.

However, I guess that could make it harder for ObjectiveGit users to understand what's _actually_ possible (vs. what's exposed), so I could go either way on it.