Sebastian Thiel

Thanks so much, @benbrittain, for your openness towards this improvement! With that added correctness, I think this will put `argh` right into the sweet spot between low-enough compile times, convenience,...

Hi @benbrittain, I think if I would hear your ideas about my initial thoughts stated above, I would consider giving the implementation a shot. That way I hope to avoid...

That sounds great, thank you! Regarding binary overhead, I would think that there is close to none, but then again I don't really know how `Argh` is working. As long...

@davidkna I think today we had a break-through as it appeared clear what features `gitoxide` needs to provide to fully replace (and accelerate) previous `git` invocations while providing support for...

### About opportunities for performance improvements @pascalkuthe I have created quick profile from running `cargo build --release --no-default-features --features max,cache-efficiency-debug --bin gix && /usr/bin/time -lp ./target/release/gix -v free pack create...

Let's not drop support in the client, by now the overhead for that seems negligible. Furthermore, `push` is still using V1 so it's probably a good exercise keep V1 in...

I just wanted to add that `prodash` is merely used, by `gix`, as an interface to transmit hierarchical progress in potentially long-running operations. Even though it provides its own renderers...

I am investigating the issue for `gitoxide` and wanted to share some findings that might be relevant for `libgit2` as well. When reproducing the issue on MacOS with this script…...

`git status` is going to happen soon and then the issue can be properly resolved.

I have updated the description to be more precise, and hope that at least one of these checkboxes can be ticked soon.