Chris Darroch

Thanks for the test repository! I was able to reproduce at least some of the inconsistent behaviour you've seen with it. To be a bit more explicit, one type of...

I would have tested the steps in https://github.com/git-lfs/git-lfs/issues/4166#issuecomment-654072795 above on macOS, with circa Git LFS 2.10. Testing again now with a recent Git LFS shows much better behaviour, where `/1kbasic...

Another issue which we have identified as likely stemming from the use of `flock(2)` for exclusive locking of inodes while checking their projection status is a significant slowdown when executing...

Hi, thanks for asking, and my apologies for the tardy response. The current status is pretty well described in https://github.com/microsoft/VFSForGit/issues/126#issuecomment-622586670, and for the sake of clarity here I'll paste in...

Hey, I'm sorry you're having trouble. I wish I had a simple suggestion, but I confess I do not. I'd be very interested in any suggestions others have, though. As...

Hey, thanks for the question. In terms of the `binary` attribute, that is actually what's known in the Git [documentation](https://git-scm.com/docs/gitattributes#_defining_macro_attributes) as a "macro attribute" that is equivalent to `-diff -merge...

First, I would definitely recommend reading through the regular Git documentation to understand how the diff and merge driver options work. Second, while I appreciate the issue where someone would...

So as I described, what you want is to configure the `git-lfs-merge-driver(1)` program as your merge driver. By default, that will invoke Git's own merge machinery after first converting any...

> So there is no other way than changing a local configuration on each individual machine? Not if you're setting the `merge.*.driver` or `diff.*.command` configurations, no. Now if using the...

Hey, I'm sorry you're having trouble. Would you be able to provide some more details by filling out the full issue template, such as the output of `git lfs env`?...