@@ -0,0 +1,80 @@
+== git-lfs-checkout(1) -- Update working copy with file content if available
+
+=== SYNOPSIS
+
+`git lfs checkout` [...] `git lfs checkout` --to
+\{--base|--ours|--theirs}
+
+=== DESCRIPTION
+
+Try to ensure that the working copy contains file content for Git LFS
+objects for the current ref, if the object data is available. Does not
+download any content; see git-lfs-fetch(1) for that.
+
+Checkout scans the current ref for all LFS objects that would be
+required, then where a file is either missing in the working copy, or
+contains placeholder pointer content with the same SHA, the real file
+content is written, provided we have it in the local store. Modified
+files are never overwritten.
+
+One or more s may be provided as arguments to restrict the set of files
+that are updated. Glob patterns are matched as per the format described
+in gitignore(5).
+
+When used with `--to` and the working tree is in a conflicted state due
+to a merge, this option checks out one of the three stages a conflicting
+Git LFS object into a separate file (which can be outside of the work
+tree). This can make using diff tools to inspect and resolve merges
+easier. A single Git LFS object's file path must be provided in .
+
+=== OPTIONS
+
+* `--base`: Check out the merge base of the specified file.
+* `--ours`: Check out our side (that of the current branch) of the
+conflict for the specified file.
+* `--theirs`: Check out their side (that of the other branch) of the
+conflict for the specified file.
+* `--to` : If the working tree is in a conflicted state, check out the
+portion of the conflict specified by `--base`, `--ours`, or `--theirs`
+to the given path.
+
+=== EXAMPLES
+
+* Checkout all files that are missing or placeholders:
+
+....
+$ git lfs checkout
+....
+
+* Checkout a specific couple of files:
+
+....
+$ git lfs checkout path/to/file1.png path/to.file2.png
+....
+
+* Checkout a path with a merge conflict into separate files:
+
+....
+# Attempt merge with a branch that has a merge conflict
+$ git merge conflicting-branch
+CONFLICT (content): Merge conflict in path/to/conflicting/file.dat
+
+# Checkout versions of the conflicting file into temp files
+$ git lfs checkout ours.dat --ours path/to/conflicting/file.dat
+$ git lfs checkout theirs.dat --theirs path/to/conflicting/file.dat
+
+# Compare conflicting versions in ours.dat and theirs.dat,
+# then resolve conflict (e.g., by choosing one version over
+# the other, or creating a new version)
+
+# Cleanup and continue with merge
+$ rm ours.dat theirs.dat
+$ git add path/to/conflicting/file.dat
+$ git merge --continue
+....
+
+=== SEE ALSO
+
+git-lfs-fetch(1), git-lfs-pull(1), gitignore(5).
+
+Part of the git-lfs(1) suite.
@@ -0,0 +1,24 @@
+== git-lfs-clean(1) -- Git clean filter that converts large files to pointers
+
+=== SYNOPSIS
+
+`git lfs clean`
+
+=== DESCRIPTION
+
+Read the contents of a large file from standard input, and write a Git
+LFS pointer file for that file to standard output.
+
+Clean is typically run by Git's clean filter, configured by the
+repository's Git attributes.
+
+Clean is not part of the user-facing Git plumbing commands. To preview
+the pointer of a large file as it would be generated, see the
+git-lfs-pointer(1) command.
+
+=== SEE ALSO
+
+git-lfs-install(1), git-lfs-push(1), git-lfs-pointer(1),
+gitattributes(5).
+
+Part of the git-lfs(1) suite.
@@ -0,0 +1,53 @@
+== git-lfs-clone(1) -- Efficiently clone a LFS-enabled repository
+
+=== SYNOPSIS
+
+`git lfs clone` [git clone options] []
+
+=== DESCRIPTION
+
+Clone an LFS enabled Git repository more efficiently by disabling LFS
+during the git clone, then performing a 'git lfs pull' directly
+afterwards.
+
+'git lfs clone' also installs all of the repo-level hooks (.git/hooks)
+that LFS requires to operate. If `--separate-git-dir` is given, the
+hooks will be installed there.
+
+This is faster than a regular 'git clone' because that will download LFS
+content using the smudge filter, which is executed individually per file
+in the working copy. This is relatively inefficient compared to the
+batch mode and parallel downloads performed by 'git lfs pull'.
+
+=== OPTIONS
+
+All options supported by 'git clone'
+
+* `-I` `--include=`: See [INCLUDE AND EXCLUDE]
+* `-X` `--exclude=`: See [INCLUDE AND EXCLUDE]
+* `--skip-repo`: Skip installing repo-level hooks (.git/hooks) that LFS
+requires. Disabled by default.
+
+=== INCLUDE AND EXCLUDE
+
+You can configure Git LFS to only fetch objects to satisfy references in
+certain paths of the repo, and/or to exclude certain paths of the repo,
+to reduce the time you spend downloading things you do not use.
+
+In your Git configuration or in a `.lfsconfig` file, you may set either
+or both of `lfs.fetchinclude` and `lfs.fetchexclude` to comma-separated
+lists of paths. If `lfs.fetchinclude` is defined, Git LFS objects will
+only be fetched if their path matches one in that list, and if
+`lfs.fetchexclude` is defined, Git LFS objects will only be fetched if
+their path does not match one in that list. Paths are matched using
+wildcard matching as per gitignore(5).
+
+Note that using the command-line options `-I` and `-X` override the
+respective configuration settings. Setting either option to an empty
+string clears the value.
+
+=== SEE ALSO
+
+git-clone(1), git-lfs-pull(1), gitignore(5).
+
+Part of the git-lfs(1) suite.