Eric Huss

`remote_callbacks.rs` has some examples for handling callbacks (using an `extern "C"` callback with a `void *` payload for the function pointer). That might provide some inspiration.

Let me try to summarize the possible problems with the issues of the system libgit2 being out of sync with the features here: System | git2-rs | Result -------|---------|-------- neither...

The `main.rs` in the repo only prints "Hello, world!". Is it perhaps missing the reproduction code?

Thanks! Can the callback take a `CStr` instead? AFAIK, the value isn't an arbitrary slice of bytes since it cannot contain a null.

Do you perhaps have `init.templateDir` configured in your global config? It defaults to using that (overriding the init options).

Thanks for putting together the reproduction. I have filed https://github.com/libgit2/libgit2/issues/6243 with upstream. A workaround is to use a refspec with a destination, as in `+d48338d82864679ed3bc656d7f7d1c445ac991b2:d48338d82864679ed3bc656d7f7d1c445ac991b2`.

Yep. I've been preparing a bump, but there are some snags that are delaying it. Hopefully soon!

Just FYI, we are migrating to triagebot, and this issue should be fixed when that happens.

Regarding the semver compatibility: Yea, the API can change across semver-incompatible releases, but we have to minimize the semver-incompatible releases because they affect plugins (plugins may need to be updated...

Thanks for the report! I'm not sure what monalisa is, but the fonts are defined by the book's CSS. In particular, code blocks use "Source Code Pro", which is a...