History

brian m. carlson 3f5fca598f docs: add support for hash algorithm detection While SHA-256 is presently considered strong, it might not always be, so we should consider supporting other hash algorithms. We anticipate that, much like Git, exactly one hash algorithm will be in use at a time per repository. To make it easier for the client and server to negotiate a suitable algorithm, let's add a field to designate the hash algorithm in batch requests. This allows the client to declare to the server the hash algorithm on first upload, and the server can respond with the hash algorithm in use (if it supports multiple) or a 409 response if it cannot handle that. We expect clients and servers to both gracefully handle the absence of this value and assume SHA-256 if not specified.		2021-09-09 16:15:43 +00:00
..
api	docs: add support for hash algorithm detection	2021-09-09 16:15:43 +00:00
howto	docs: prepare for rename of default branch name	2021-02-02 14:40:51 +00:00
man	ssh: support concurrent transfers using the pure SSH protocol	2021-07-20 19:15:59 +00:00
proposals	docs: add support for hash algorithm detection	2021-09-09 16:15:43 +00:00
custom-transfers.md	Fix typo 'initiation'	2019-08-22 00:24:14 +02:00
extensions.md	Fix typo	2015-10-06 01:11:55 +09:00
linux-build.md	Remove trailing whitespace	2018-10-03 20:34:13 +00:00
README.md	Allow using custom transfer agents directly	2017-07-31 16:28:07 +02:00
spec.md	docs/spec: document that pointer files are unique	2019-12-09 22:08:19 +00:00

Git LFS Documentation

Reference Manual

Each Git LFS subcommand is documented in the official man pages. Any of these can also be viewed from the command line:

$ git lfs help <command>
$ git lfs <command> -h

Details of how the Git LFS client works are in the official specification.

Details of how the GIT LFS server works are in the API specification.