ConcurrentCrab

@lafriks adressed the url joins.

@techknowlogick dropped the vendoring commit. I believe everything looks good from my side now. If this PR looks satisfactory to you, and once you've tested and verified that all functionality...

Also, there's no way to selectively identify older `git-lfs` clients and just disable the SSH protocol for them, as the protocol doesn't have a user-agent identifier (it's been discussed several...

Alternatively, I suppose, we can add a default-false config option to let users decide when it would be appropriate for their needs? It can be turned default-true once the "updated...

Hey all, Just wanted to do a quick ping to ask if you've had the chance to look at this yet.

@techknowlogick added a new commit adding a `LFS_ALLOW_PURE_SSH` option to the `server` section. It's default-false due to the zero value. It can be later set to default-true. But like I...

The documentation blurb could be something like: > **LFS Pure SSH Protocol Support** > The LFS protocol supports connecting purely over SSH (without exposing an HTTP endpoint). > Support for...

> > The documentation blurb could be something like: > > > **LFS Pure SSH Protocol Support** > > > The LFS protocol supports connecting purely over SSH (without exposing...

@lunny made https://gitea.com/gitea/docs/pulls/49

@delvh changed to use `container.Set`.