Chris Darroch

I'm going to close this as there's been no followup recently, but if it is still relevant, please do reopen it. Thanks!

Our container builds are on 1.21.1 already (see PR git-lfs/build-dockers#59) so the next Git LFS release will use at least that version.

@MaddaliManeesh -- this is a fairly old issue, but I suspect the underlying issue remains. I can't comment on the Beyond Compare tool as I'm not familiar with it. Also...

Hey, thanks for your question! It's true that support for a pure SSH protocol has been added to the Git LFS client. However, so far as I know, none of...

As I updated the wiki to reflect the current state of affairs, I'm going to close this issue, but please feel free to offer additional suggestions in PRs or further...

Unfortunately, I'm not sure this is feasible at the moment, but I'll mark it as a potential enhancement to add an `--object-id` option to `git-lfs-fetch(1)`. Note that you would still...

Hey, thanks for the report and the detailed reproduction script! I think this gives us a lot of scope for analysis. We probably want to investigate a few things to...

Hey, I'm sorry you're having trouble. I'm not sure what would be causing this, because it depends a lot on how you've configured your system and repository. If you are...

> i just purchase lfs data pack but why i am still have this issue First, please create a separate issue when asking about a different problem than was originally...

Another use case example for this functionality turned up while working on git-lfs/git-lfs#5236, namely, that the `ruby/setup-ruby@v1` action [sets](https://github.com/ruby/setup-ruby/blob/4b2d1d631efa087f8896c15a0c6023dc2f483198/index.js#L177) the `TMPDIR` environment variable for subsequent steps, but for the Git...