brian m. carlson

Hey, Git LFS doesn't cause Git to exit with a certain status code. An exit code with status 141 means that the process received SIGPIPE, which means it tried to...

Hey, Thanks for the report. Can you tell me whether you're using the pure SSH protocol or the legacy hybrid protocol? Also, can you provide the output of `GIT_TRACE=1` so...

Hey, Thanks for the log. I think I know where the problem probably lies, and I'll put this on the v3.3.0 milestone to see if we can improve this.

I believe Git will use its built-in `GIT_EXEC_PATH` before the system `PATH`. If you run `git --exec-path`, and there's a `git-lfs` or `git-lfs.exe` binary in there, then you'd need to...

Nope, we're tracking this in #4002 and it's marked help-wanted. We need someone familiar with Windows and the appropriate installer tooling to help us handle that.

Hey, In general, having the client produce custom attributes is going to be tricky, since the client doesn't execute any custom code to determine this data. We could add some...

I agree this sounds like it would be achievable. Can you open a PR with documentation to `docs/proposals` that would describe the extension to the locking API? Once that's open,...

Hey, Sorry to hear you're having trouble. First, about the restarts, Git LFS should not be able to cause your computer to restart, so if that happens, it could be...

There are two pieces of an upload process, the actual upload of the file and the verification process. If there's a large delay during the verification process, the verification will...

Hey, If the Git LFS process has exited (such as after the push has failed), then the memory should be freed by the operating system. If it's not, it's likely...