68c0e18d05
* Add HTTP 507 (Insufficient Storage) to the list of optional statuses Mention that the server implementation may optionally return status code 507. This does not add any specific handling of 507 in either the client or the test server implementation. If a server returns this status code, it will be handled by the client as a generic "Server Error". See #1327 and #1438. Change-Id: I2de691bb57b3ef44288b91b79226695f768ec44e Signed-off-by: David Pursehouse <dpursehouse@collab.net> * Add default error messages for 427, 507 and 509 responses Change-Id: Ia42731e35f2aa7b918de3d0412205700df968d95 Signed-off-by: David Pursehouse <dpursehouse@collab.net> |
||
---|---|---|
.. | ||
api | ||
man | ||
proposals | ||
custom-transfers.md | ||
extensions.md | ||
linux-build.md | ||
README.md | ||
spec.md |
Git LFS Documentation
Reference Manual
Each Git LFS subcommand is documented in the official man pages. Any of these can be viewed from the command also:
$ git lfs help <command>
$ git lfs <command> -h
Videos
- How to Work with Big Files - Quick intro to Git LFS.
Developer Docs
Details of how the Git LFS client works are in the official specification. There is also an API specification that describes how the server works.