Robert Coup

Use case: safely setting up piping via xargs is annoying when git-lfs is being called from Python.

> I'm a little interested in your use case for this. For example, a git+lfs repository containing large data files of some flavour that are HTTP-consumable. In the geospatial world,...

@bk2204 thanks! FYI, if I don't get time for it in the next week it's likely to be mid-August until I get back to it again.

@bk2204 reviving this because it fits into a use-case of ours, similar to @mitar's original... again, read-only, and for datasets published publicly. 1. I can't really see the point of...

(Rearranged slightly) > The desire as I understand it is to provide an approach that can be served entirely statically without the need for a server. The original desire, and...

@bk2204 any further thoughts here?

okay, so brainstorming what that could look like: 1. the LFS server needs to know about what the externally stored object URLs _are_: an OID→URL-list mapping 2. so when a...

> It is download only, because in order to effectively and correctly upload, you need WebDAV and locking (see the Git dumb protocol), and we aren't going to implement that....

> My goal here is for folks to be able to use a static website for the purpose of hosting LFS content, which should let folks use arbitrary web URLs...

TBC, I'm not against manifests for downloading. I personally don't think they add much, but ok. > If you want to not have to have a Git LFS operation download...