Kim Altintop

This is actually possible, though not too obvious from just looking at the API: ``` haskell let (bits,nh) = suggestSizing 3 0.1 hfam = cheapHashes nh filt = fromList hfam...

It is potentially interesting to note that `git.git` repacks refs when more than one is updated in a transaction (for `—atomic` support). Last time I checked, `libgit2` doesn’t do that,...

Oh my yes reflogs. I do think they’re a performance sink, which is why they are disabled by default for bare repos. I did, however, end up recently forcing creation...

> if there are too many events I misspoke there, it's more related to the `notify` _crate_ not allowing the set event masks for portability reasons, and also the inherent...

This all looks good, will give it a spin shortly! > As an interesting chunk of information I may add that I tried to close the connection but am unable...

> Transport::close() was actually a misnomer Are you sure though that the inner writer doesn't need to be flushed?

Relying on `Drop` seems a bit hairy in the async variants, unless you can keep track of a waker (and even then...). Maybe better to leave it to the caller.

Edit: `ref-prefix`, not `want-ref`. In the example, one might think that the client could have noticed that it is about to request an empty pack (and that’s probably true). However,...

Oh wait, the server is not actually sending anything, that’s the client’s `done`. I wonder if that should be considered a bug in `upload-pack`.

Yes timeouts on the receive channel would be a good idea in general, although I'm not sure offhand how much this would have to be protocol-aware. A well-behaved server would...