Expose libgit2 reference database backend for managed code refdb impls.#392
Closed
ethomson wants to merge 1 commit into
Closed
Expose libgit2 reference database backend for managed code refdb impls.#392ethomson wants to merge 1 commit into
ethomson wants to merge 1 commit into
Conversation
Member
Author
There was a problem hiding this comment.
Is this weird? I started out with having this return a simple object like RefdbReference but I moved it back to this.
Member
|
Closed in favor of #401 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'd like to write a refdb backend in managed code, so here's some bindings for that!
This was very much modeled after the odb backend work, especially since my pinvoke-fu is weak.
Please note that this depends on libgit2 PR 1464 so this is definitely not ready for merge until we do some updates to the libgit2 version.