Sebastian Thiel

I think this is a stroke of genius! But let me explain! Having a `gix-error` crate was a strong itch after the recent drama when I thought about removing `thiserror`...

That's a valid point, thanks for bringing it up (*I didn't think of it*)! The end-user should be the one who choses, and those in-between libraries would then not be...

❤️ This is even more bold than I originally stated (if I understand it correctly) as it would be much like `anyhow`, but for libraries. As long as it's possible...

> Thanks @Byron I had accepted the invitation, though I have to finish the gix-macors PR first. Great, thanks so much! > Though I do think that keep making new...

I have added as many feature toggles as possible and will cut a new release now. The recommendation is to go with `default-features = false` and then re-add all components...

Fixed, thanks!

Thanks so much for offering, I think this is a great place to talk! During The Merge @extrawurst and I talked about `blame` a little bit and concluded that this...

The API for obtaining branches related to remotes has been overhauled in [the linked PR](https://github.com/Byron/gitoxide/pull/1181) and you should be able to replace the existing code with it fully. You will...

It turns out that `gix` knows the following about that: ``` ❯ gix config-tree | rg sslVerify 🤔 http.sslVerify not planned ℹ on demand ℹ ``` It's indeed not implemented...

Thanks for sharing! I am quite sure that eventually this will be implemented as `gix` has a real opportunity to be more compatible to Windows than `git` is.