git lfs fetch a range of commits about git-lfs HOT 2 OPEN

Hey,

I'm not sure of a good way to go about doing this in an efficient way. You probably want to use git rev-list A..B --not --remotes=dest (where dest is the destination remote), which will make this a lot more efficient and avoid traversing all objects that are already on the destination, but it's still not going to be screamingly performant.

We internally use git cat-file --batch to make it more efficient to find the objects without spawning a large number of Git processes, which you can do, too. You can also use git cat-file --batch-check first to find those items which are pointer files (which must be less than 1024 bytes), since sometimes people mark a file as an LFS file and then push the large object anyway. However, this will likely require more work than a simple shell one-liner, so you might want to write something like a Ruby script to handle this.

I think what you want here for scripting is an equivalent to git lfs push's --object-id flag, which unfortunately doesn't exist yet. It shouldn't be too hard to add if you're interested, but it's ultimately going to be rather difficult to handle as part of scripting without adding that functionality.

from git-lfs.

Yeah, I ended up solving this using a Python script which did something along the lines of my original post, except that rather than passing revisions to git lfs fetch, it was easier to directly pipe LFS pointer file content to git lfs smudge (discarding the output, but taking advantage of the fact that it caused the object to be downloaded).

And yes, supporting --object-id for git lfs fetch would be nice and would avoid needing to do the smudge shenanigans. Ideally LFS would expose facilities for synchronizing remote/local LFS object stores without needing to touch commits - push --object-id is half of that story, but we're missing a corresponding fetch piece.

from git-lfs.