Sebastian Thiel

Thank you for clarifying that. From my experience, using `gix` in the frontend has advantages in terms of compatibility at the very least, but I also hear that recently `libgit2`...

Thanks a lot for writing all this down! All this sounds familiar, particularly the multi-step process of downloading packs for different refs. If I remember correctly, the server-side is a...

I see, thanks for the update! Speaking off, the employment-idea at GitButler fell through, but I am doing some freelance work for them to integrate `gitoxide`. Internally I'd reconsider employment...

I really appreciate your research, it's making tech-debt obvious that thus far I was conveniently able to ignore. With the abandonment of `git-lfs` a decision was made that it has...

> Are such binaries cached and reused even if, between test runs, `git restore .` and `gix clean -xde` are used? I did that each time here. Yes, they are...

Oh, yes, sorry, I didn't read carefully enough. Indeed, then `target/` would be wiped and the rebuild happens. `cargo` is able to deal with multi-process activity, while the tests that...

The issue might [originate here](https://github.com/Byron/gitoxide/blob/f8ce3d0721b6a53713a9392f2451874f520bc44c/gix/src/create.rs#L210-L229) which is the only spot where it writes the local configuration. It's a well-known limitation that in-memory configuration can't be written back yet, merely because...

That's…interesting, as I also don't know how I would have fixed that. There were a few changes related to cloning, but nothing that would have affected the configuration that is...

Thanks for the re-test and the update to the issue! This means that once the global configuration for symlinks is respected, along with other values that it wants to put...

Thanks for all the research! > I believe users should not set those variables in the global scope. They seem reasonable not to honor from the global scope, but I...