Taylor Blau

> I don't feel like an improvement in the protocol really addresses the issue -- even bringing the speed per lock down by a factor of ten (.3 seconds per...

> Moreover, you don't have to establish a new HTTPS connection for each > lock request [ ... ] Right, though I'm not sure if we're doing this in practice....

Yes, this would be quite a neat feature to have, though I'm not sure it's possible. When a message begins with a `/`, slack tries to send it to `@slackbot`,...

Hi @NeverNotGlow, thanks for opening this issue. I am certainly in favor of something like this, though it will have to be introduced in a backwards-compatible fashion. In practice, we...

@git-lfs/core what do you think?

> I think we could simply try a `/locks/batch` API and fall back to the > existing API if we get a 404. I think that's a good idea; it...

> I think there's earlier gains that could be made here, given that > it'll likely take some time for all servers to support this. I want to first say...

Hi @jerick1976, thanks for opening this and sorry that it slipped through my filter. I am a little confused on the details, so here are a few questions that we...

> In general, our pattern matching in this library doesn't match Git's behavior. I'm not sure that I agree. Special care was taken to port the tests from upstream's t0370...

> We definitely have some odd behavior around wildcards. Some of these are probably unintentional bugs that I wrote when trying to match all of these test-cases, but the remainder...