Explain a subtlety of client handling for "download" batch action
Explain a subtlety of client handling for "download" batch action

The LFS client uses the presence of the "download" action on an "upload" request to deduce that the object content is already present on the server: the object content must be present, or the server could not offer a "download" action. Since the server already knows the object content, the client does not need to upload a new copy and can skip the transfer step.

Make this interaction between the client and server explicit in the documentation.
github/git-lfs,github/git-lfs,larsxschneider/git-lfs,github/git-lfs,andyneff/git-lfs,dakotahawkins/git-lfs,dakotahawkins/git-lfs,bozaro/git-lfs,andyneff/git-lfs,ttaylorr/git-lfs,aleb/git-lfs,andyneff/git-lfs,ttaylorr/git-lfs,Jericho25/-git-lfs_miilkyway,dakotahawkins/git-lfs,bozaro/git-lfs,aleb/git-lfs,ttaylorr/git-lfs,larsxschneider/git-lfs,bozaro/git-lfs,Jericho25/-git-lfs_miilkyway,aleb/git-lfs,Jericho25/-git-lfs_miilkyway,larsxschneider/git-lfs