Initial commit

.gitattributes

@@ -25,3 +25,4 @@ saved_model/**/* filter=lfs diff=lfs merge=lfs -text
 *.zip filter=lfs diff=lfs merge=lfs -text
 *.zstandard filter=lfs diff=lfs merge=lfs -text
 *tfevents* filter=lfs diff=lfs merge=lfs -text
+*.psd filter=lfs diff=lfs merge=lfs -text

CHANGELOG.md

@@ -0,0 +1,2032 @@
+# Git LFS Changelog
+
+## 3.0.2 (28 Oct 2021)
+
+This release is a bugfix release which fixes a variety of problems seen since
+3.0.0, including problems with empty files, `git lfs fsck --pointers`, and
+the testsuite.
+
+We would like to extend a special thanks to the following open-source
+contributors:
+
+* @fh1ch for patches to make things work better on Alpine Linux
+* @pyckle for fixing our handling of filenames in `git lfs migrate import`
+* @ycongal-smile for fixing `git lfs migrate import` with similarly named files
+
+### Bugs
+
+* Fix two types of misdetection in git lfs fsck #4697 (@bk2204)
+* lfs: don't flag non-LFS files as invalid pointers #4691 (@bk2204)
+* git: honor GIT_OBJECT_DIRECTORY #4686 (@bk2204)
+* migrate: properly escape blob filenames #4683 (@pyckle)
+* ls-files: don't process empty files as pointers #4681 (@bk2204)
+* Call migrate() BlobFn on every blob #4671 (@ycongal-smile)
+* Correct t-lock regular expression to be musl compatible #4673 (@fh1ch)
+
+### Misc
+
+* Allow git-lfs-transfer integration tests to be skipped #4677 (@fh1ch)
+* Make CI environment GIT prefix grep more specific #4678 (@fh1ch)
+
+## 3.0.1 (28 Sep 2021)
+
+This release is a bugfix release which fixes the Windows ARM64 build process and
+addresses a regression in support for empty files in pull and fetch.
+
+We would like to extend a special thanks to the following open-source
+contributors:
+
+* @dennisameling for fixing support for Windows on ARM64
+
+### Bugs
+
+* Fix Windows arm64 release #4647 (@dennisameling)
+* fs: specify a file as existing if it's empty #4654 (@bk2204)
+
+## 3.0.0 (24 Sep 2021)
+
+This release is a major new release and introduces several new features, such as
+a pure SSH-based protocol, packages for several new OS versions, support for
+ARM64 Windows, Git-compatible pattern matching, and locking multiple files on
+the command line, among other items.
+
+When connecting over SSH, the first attempt will be made to use
+`git-lfs-transfer`, the pure SSH protocol, and if it fails, Git LFS will fall
+back to the hybrid protocol using `git-lfs-authenticate`.  Note that no major
+forges are known to support the pure SSH protocol at this time.
+
+Because it is a major release, we've made some backwards-incompatible changes.
+A (possibly incomplete) list of them is as follows:
+
+* NTLM support has been completely removed, since nobody volunteered to fix
+  issues in it.  Users are advised to use Kerberos or Basic authentication
+  instead.
+* When using an SSH URL (that is, the syntax starting with `ssh://`), the
+  leading slash is not stripped off when invoking `git-lfs-authenticate` or
+  `git-lfs-transfer`.  This is compatible with the behavior of Git when invoking
+  commands over SSH.
+* `git lfs fsck` now additionally checks that pointers are canonical and that
+  files that are supposed to be LFS files actually are.  It also exits nonzero
+  if any problem is found.
+* Pattern matching should be stricter and should either match the behavior of
+  `.gitattributes` or `.gitignore`, as appropriate.  Deviations from Git's
+  behavior will henceforth be treated as bugs and fixed accordingly.
+* Git LFS will now write a Git LFS repository format version into the
+  repository.  This is designed to allow future extension with incompatible
+  changes.  Repositories without this version will be assumed to be version 0.
+  Note that this is different from, but modeled on, Git's repository format
+  version.
+* `git lfs lock` and `git lfs unlock` now handle multiple pathname arguments and
+  the JSON format has changed to handle multiple responses.
+* The Go package name now contains a version number.  This should have no effect
+  on users because we don't provide a stable Go ABI.
+* Empty components in `PATH` are no longer treated as the current directory on
+  Windows because unintentionally having such empty components is common and the
+  behavior was surprising.
+
+We would like to extend a special thanks to the following open-source
+contributors:
+
+* @codykrieger for ensuring that we process includes correctly
+* @corngood for fixing a hang in prune
+* @dennisameling for adding support for Windows on ARM64
+* @fh1ch for fixing our 429 handling
+* @geki-yaba for fixing problems with askpass on Cygwin
+* @gison93 for fixing a bug in our documentation
+* @jvimr for ensuring our Debian packages are built properly
+* @opohorel for ensuring our copyright notices were up to date
+* @rhansen for fixing systems where / is a repository
+* @sergiou87 for improving support for cross builds
+* @slonopotamus for improving our error handling
+* @stanhu for improving our handling of invalid OIDs
+* @Timmmm for improving our support of .lfsconfig
+* @tklauser for avoiding the need for cgo on macOS
+
+### Features
+
+* Advertise hash algorithm supported in batch request #4624 (@bk2204)
+* Bump package version to v3 #4611 (@bk2204)
+* Update OS versions #4610 (@bk2204)
+* Add support for Debian 11 #4592 (@bk2204)
+* Support for locking and unlocking multiple files #4604 (@bk2204)
+* Add support for Windows ARM64 #4586 (@dennisameling)
+* LFS repository format version #4552 (@bk2204)
+* Pure SSH-based protocol #4446 (@bk2204)
+* Make fsck able to check for invalid pointers #4525 (@bk2204)
+* Add --fixup option to migrate info command #4501 (@chrisd8088)
+* Allow reporting of LFS pointers separately in migrate info command #4436 (@chrisd8088)
+* Add config variables for default remotes #4469 (@bk2204)
+* Make lfshttp package builds more portable #4476 (@bk2204)
+* Mark skipdownloaderrors as safe #4468 (@Timmmm)
+* Make migrate commands default to preserving uncommitted changes #4454 (@chrisd8088)
+* Darwin ARM64 support #4437 (@bk2204)
+* tools: implement cloneFileSyscall on darwin without cgo #4387 (@tklauser)
+* prune: add options to be more aggressive about pruning #4368 (@bk2204)
+
+### Bugs
+
+* corrected debian 11 & 12 derived variants #4622 (@jvimr)
+* urlconfig: anchor regexp for key matching #4598 (@bk2204)
+* filepathfilter: always use Git-compatible pattern matching #4556 (@bk2204)
+* debian and rpm: Pass `--skip-repo` to `install` and `uninstall` #4594 (@rhansen)
+* Fix hang in prune #4557 (@corngood)
+* Disable ANSI color codes while log parsing and anchor diff regular expressions #4585 (@chrisd8088)
+* Fix 429 retry-after handling for LFS batch API endpoint #4573 (@fh1ch)
+* go.mod: bump gitobj to v2.0.2 #4555 (@bk2204)
+* Fix locking with multiple paths and absolute paths #4535 (@bk2204)
+* locking: avoid nil pointer dereference with invalid response #4509 (@bk2204)
+* migrate import: make --above affect only individual files #4512 (@bk2204)
+* fs: be a little less aggressive with cleanup #4490 (@bk2204)
+* Fix downloadFile in gitfilter_smudge.go to actually propagate all errors #4478 (@slonopotamus)
+* Translate Cygwin path patches for askpass helper and cert dir/file #4473 (@geki-yaba)
+* Avoid panic on SIGINT by skipping cleanup when config uninitialized #4463 (@chrisd8088)
+* Parse stash log entries parsimonously in prune command #4449 (@chrisd8088)
+* docs: note that -I and -X override configuration settings #4442 (@bk2204)
+* Make all checks of blobSizeCutoff consistent #4435 (@chrisd8088)
+* Fix up handling of the "migrate info" command's --top option #4434 (@chrisd8088)
+* Tighten LFS pointer regexp #4421 (@stanhu)
+* invoke git-config with --includes to ensure it always evaluates `include.*` directives #4420 (@codykrieger)
+* Canonicalize Windows paths like Git does #4418 (@bk2204)
+* lfsapi: don't warn about duplicate but identical aliases #4413 (@bk2204)
+* lfs: don't invoke diff drivers when pruning repositories #4407 (@bk2204)
+* Consider scheme of request URL, not proxy URL, when choosing proxy #4396 (@bk2204)
+* Makefile: allow make release to be run twice in a row #4344 (@bk2204)
+* Makefile: don't fail the second time macOS builds are built #4341 (@bk2204)
+
+### Misc
+
+* subprocess: don't treat empty PATH component as . on Windows #4603 (@bk2204)
+* Switch from which to command -v #4591 (@bk2204)
+* Bump Go to 1.17 #4584 (@dennisameling)
+* Add cautions about unstable Go API and fix GPG key link #4582 (@chrisd8088)
+* Update go.mod module path with explicit v2 #4575 (@chrisd8088)
+* Drop unused ClearTempStorage() transfer adapter method and tune stale comments #4554 (@chrisd8088)
+* README: improve steps for building from source #4527 (@bk2204)
+* Update license year #4513 (@opohorel)
+* docs/man: add note re post-import use of checkout #4504 (@chrisd8088)
+* Bump transitive dependencies #4502 (@bk2204)
+* script/packagecloud: update distros #4494 (@bk2204)
+* Use host architecture and OS when running `go generate` #4492 (@sergiou87)
+* Bump go-spnego to the latest version #4482 (@bk2204)
+* Update git-lfs-migrate man page and add description section #4458 (@chrisd8088)
+* update x/text and dependencies #4455 (@opohorel)
+* Use blobSizeCutoff in clean pointer buffer length check #4433 (@chrisd8088)
+* tools: unset XDG_CONFIG_HOME for filetools test #4432 (@chrisd8088)
+* vendor,go.{mod,sum}: update x/net and dependencies #4398 (@chrisd8088)
+* Remove NTLM #4384 (@bk2204)
+* gitobj 2.0.1 #4348 (@bk2204)
+* Fix numbered list in git lfs examples #4347 (@gison93)
+* Add test for download gzip transport compression #4345 (@bk2204)
+
+## 2.13.3 (26 Mar 2021)
+
+This release fixes two bugs that caused `git lfs prune` to hang, updates some
+dependencies to versions which lack a security issue (which did not affect Git
+LFS), and adds support for ARM64 builds on macOS.
+
+### Bugs
+
+* lfs: don't invoke diff drivers when pruning repositories #4407 (@bk2204)
+* Parse stash log entries parsimonously in prune command #4449 (@chrisd8088)
+
+### Misc
+
+* Darwin ARM64 support #4437 (@bk2204)
+* vendor,go.{mod,sum}: update x/net and dependencies #4398 (@chrisd8088)
+
+## 2.13.2 (13 Jan 2021)
+
+This release introduces a security fix for Windows systems, which has been
+assigned CVE-2021-21237.
+
+On Windows, if Git LFS operates on a malicious repository with a git.bat or
+git.exe file in the current directory, that program is executed, permitting the
+attacker to execute arbitrary code.  This security problem does not affect Unix
+systems.  This is the same issue as CVE-2020-27955, but the fix for that issue
+was incomplete and certain options can still cause the problem to occur.
+
+This occurs because on Windows, Go includes (and prefers) the current directory
+when the name of a command run does not contain a directory separator.  This has
+been solved by always using PATH to pre-resolve paths before handing them to Go.
+
+We would like to extend a special thanks to the following open-source
+contributors:
+
+* @Ry0taK for reporting this to us responsibly
+
+### Bugs
+
+* Use subprocess for invoking all commands (@bk2204)
+
+## 2.13.1 (11 Dec 2020)
+
+This release fixes a bug in our build tooling that prevents our release process
+from working properly.  This release is otherwise identical to 2.13.0.
+
+### Misc
+
+* Makefile: don't fail the second time macOS builds are built #4341 (@bk2204)
+
+## 2.13.0 (10 Dec 2020)
+
+This release introduces several new features, such as the `--above` option to
+`git lfs migrate import` and support for `socks5h` proxies.  In addition, many
+bugs have been fixed and several miscellaneous fixes have been included.
+
+Unless someone steps up to fix and maintain NTLM support, this will be the last
+Git LFS release to support NTLM.  See #4247 for more details.  Note that Git LFS
+supports Kerberos as well, which is far more secure and may be a viable
+replacement in many situations.
+
+We would like to extend a special thanks to the following open-source
+contributors:
+
+* @EliRibble for adding support for the `--above` option to `git lfs migrate import`
+* @andrewshadura for adding support for the `GIT_LFS_SKIP_PUSH` environment variable
+* @sinbad for fixing problems with retaining objects used by stashes
+* @tklauser for cleaning up our use of error constants in the code
+
+### Features
+
+* Add --above parameter to 'migrate import'. #4276 (@EliRibble)
+* Add GIT_LFS_SKIP_PUSH to allow skipping the pre-push hook #4202 (@andrewshadura)
+* lfshttp: add support for socks5h proxies #4259 (@bk2204)
+* Add manual pages to release assets #4230 (@bk2204)
+* Honor GIT_WORK_TREE #4269 (@bk2204)
+
+### Bugs
+
+* Make git lfs migrate import handle missing extensions #4318 (@bk2204)
+* fs: don't panic when using a too-short object ID to push #4307 (@bk2204)
+* Fix pattern matching for .gitattributes #4301 (@bk2204)
+* config: map missing port to default for HTTP key lookups #4282 (@bk2204)
+* tools: use IoctlFileClone from golang.org/x/sys/unix #4261 (@tklauser)
+* tools/util_darwin.go: Remove use of direct syscalls #4251 (@stanhu)
+* tools: always force a UTF-8 locale for cygpath #4231 (@bk2204)
+* prune: fix deleting objects referred to by stashes #4209 (@sinbad)
+
+### Misc
+
+* migrate import: warn about refs on case insensitive file systems #4332 (@larsxschneider)
+* Drop obsolete OS support #4328 (@bk2204)
+* tools: use ERROR_SHARING_VIOLATION const from golang.org/x/sys/windows #4291 (@tklauser)
+* pull: gracefully handle merge conflicts #4289 (@bk2204)
+* script/upload: avoid using Ruby's URI.escape #4266 (@bk2204)
+* add documentation of security bug report process #4244 (@chrisd8088)
+
+## 2.12.1 (4 Nov 2020)
+
+This release introduces a security fix for Windows systems, which has been
+assigned CVE-2020-27955.
+
+On Windows, if Git LFS operates on a malicious repository with a git.bat or
+git.exe file in the current directory, that program is executed, permitting the
+attacker to execute arbitrary code.  This security problem does not affect Unix
+systems.
+
+This occurs because on Windows, Go includes (and prefers) the current directory
+when the name of a command run does not contain a directory separator.  This has
+been solved by always using PATH to pre-resolve paths before handing them to Go.
+
+We would like to extend a special thanks to the following open-source
+contributors:
+
+* @dawidgolunski for reporting this to us responsibly
+
+### Bugs
+
+* subprocess: avoid using relative program names (@bk2204)
+
+## 2.12.0 (1 Sep 2020)
+
+This release introduces several new features, such as support for the SHA-256
+repositories coming in a future version of Git, restored support for Go 1.11,
+the ability to read the contents of .lfsconfig from the repository, signed and
+notarized binaries on macOS, and pre-built 32-bit ARM binaries on Linux.  In
+addition, several bugs have been fixed and miscellaneous fixes included.
+
+Note that macOS releases are now shipped as zip files, not tarballs, since it is
+not possible to notarize tarballs.  macOS releases are now also built on macOS,
+so `git lfs dedup` should now function.
+
+We would like to extend a special thanks to the following open-source
+contributors:
+
+* @saracen for adding support for ARM binaries
+* @mversluys for improving locking support
+* @cccfeng for updating our documentation to make it more readable
+* @bluekeyes for improving performance and tracing
+* @gertcuykens for adding missing parts of our documentation
+
+### Features
+
+* config: optionally read .lfsconfig from the repository #4200 (@bk2204)
+* Support SHA-256 repositories #4186 (@bk2204)
+* allow Go 1.11 builds by using WaitStatus.ExitStatus() #4183 (@chrisd8088)
+* add --worktree option to install and uninstall commands #4159 (@chrisd8088)
+* Sign and notarize binaries on macOS #4143 (@bk2204)
+* Makefile: add linux arm build and release targets #4126 (@saracen)
+* Allow locking and unlocking non-existent files #3992 (@mversluys)
+
+### Bugs
+
+* docs/api/locking: add an explicit <br> #4208 (@cccfeng)
+* Fix hang when the user lacks permissions #4207 (@bk2204)
+* Don't mark unlocked files that aren't lockable as read-only #4171 (@bk2204)
+* locking: make patterns with slashes work on Windows #4139 (@bk2204)
+* git: consider full refspec when determining seen refs #4133 (@bk2204)
+
+### Misc
+
+* Fix Windows CI #4199 (@bk2204)
+* Fix testsuite when working with non-master default branch #4174 (@bk2204)
+* git: improve performance of remote ref listing #4176 (@bluekeyes)
+* subprocess: trace all command execution #4175 (@bluekeyes)
+* Update git-lfs-migrate.1.ronn #3869 (@gertcuykens)
+* t: use repo v1 with extensions #4177 (@bk2204)
+* Makefile: ensure temp Go modules can be deleted #4157 (@chrisd8088)
+* Improve test suite robustness via environment #4132 (@bk2204)
+
+## 2.11.0 (8 May 2020)
+
+This release introduces several new features, such as better support for unnamed
+local paths and URLs as remotes, support for `submodule.recurse`, exponential
+backoff on failure, and support for renegotiation.  In addition, numerous bugs
+have been fixed and miscellaneous issues have been addressed.
+
+We would like to extend a special thanks to the following open-source
+contributors:
+
+* @bluekeyes for adding support for exponential backoff
+* @pluehne for adding support for `submodule.recurse`
+* @Electric26 for fixing the default behavior of a prompt
+* @nataliechen1 for fixing certain upload retry failures
+* @shalashik for fixing a panic during cherry-pick
+* @swisspol for updating our documentation to reflect supported `.lfsconfig`
+  keys
+* @dan2468 for updating the copyright year
+
+### Features
+
+* Allow literal local paths as remotes #4119 (@bk2204)
+* pre-push: find named remote for URL if possible #4103 (@bk2204)
+* tq: add exponential backoff for retries #4097 (@bluekeyes)
+* migrate import: set text to unspecified for excluded fields #4068 (@bk2204)
+* Update list of distros for packagecloud.io #4080 (@bk2204)
+* lfshttp: allow renegotiation #4066 (@bk2204)
+* Support submodule.recurse = true #4063 (@pluehne)
+* add man page for the post-commit hook command #4052 (@chrisd8088)
+* Add an option to control warning about files larger than 4 GiB #4009 (@bk2204)
+
+### Bugs
+
+* commands/command_migrate.go: fix bug #4116 (@Electric26)
+* git: avoid "bad object" messages when force-pushing #4102 (@bk2204)
+* git: avoid trying to rewrite remote tags as remote branches #4096 (@bk2204)
+* make Go tests run consistently using local binary #4084 (@chrisd8088)
+* commands: don't honor lfs.fetch* for ls-files #4083 (@bk2204)
+* commands: print help output with --help #4059 (@bk2204)
+* fail dedup command with explanation when LFS extensions configured #4045 (@chrisd8088)
+* fix upload retry 'file already closed' issue' #4042 (@nataliechen1)
+* commands/command_filter_process: cherry-pick of several commits cause panic error #4017 (@shalashik)
+* Check error when creating local storage directory #4016 (@bk2204)
+* track: detect duplicate patterns with --filename #4000 (@bk2204)
+
+### Misc
+
+* Removed lfs.extension.* from list of supported keys for .lfsconfig #4044 (@swisspol)
+* Tidy modules #4035 (@bk2204)
+* README: explain how to verify releases #4022 (@bk2204)
+* docs: document git lfs migrate --yes #4023 (@bk2204)
+* Stop using cgo on amd64 Linux #4026 (@bk2204)
+* updated copyright year #3995 (@dan2468)
+
+## 2.10.0 (21 January 2020)
+
+This release introduces several new features, such as support for local paths in
+remotes, Kerberos support, and official binaries for S390x and little-endian
+64-bit PowerPC systems.  In addition, numerous bugs have been fixed and
+miscellaneous issues have been addressed.
+
+We would like to extend a special thanks to the following open-source
+contributors:
+
+* @ganadist for fixing a bug in the output of `git lfs env`
+* @exceed-alae for fixing a possible nil pointer dereference
+* @slonopotamus for improvements to Windows support and code cleanups
+* @nataliechen1 for fixing a data race
+* @ssgelm for writing and updating the code to use a new cookie jar parser
+* @austintraver for improving the output of `git lfs status`
+* @nikola-sh for improving option parity with Git
+* @alrs for fixing several error checks in the testsuite
+* @pluehne for improving our support for uncommon references
+
+### Features
+
+* Optimize pushes for multiple refs #3978 (@bk2204)
+* Include ppc64le and s390x Linux builds in releases #3983 (@bk2204)
+* Kerberos (SPNEGO) support for HTTP #3941 (@bk2204)
+* Add support for local paths #3918 (@bk2204)
+* Allow specifying HTTP version to use #3887 (@bk2204)
+
+### Bugs
+
+* t-duplicate-oids: use correct awk indexing #3981 (@bk2204)
+* Improved proxy support #3972 (@bk2204)
+* install: don't print error if run outside repository #3969 (@bk2204)
+* debian: bump version of golang-go #3959 (@bk2204)
+* lfshttp: Set valid default value for lfs.concurrenttransfers #3949 (@ganadist)
+* Add nil-check on defer block of DoTransfer() #3936 (@exceed-alae)
+* Retry batch failures #3930 (@bk2204)
+* rpm: use old setup code on CentOS 7 #3938 (@bk2204)
+* Interpret relative hook paths as relative to working tree #3926 (@bk2204)
+* Handle missing cygpath gracefully #3910 (@bk2204)
+* Update index before showing status #3921 (@bk2204)
+* Honor lfs.url when deciding on transfer adapters #3905 (@bk2204)
+* Implement retry logic to fix LFS storage race conditions on Windows #3890 (@slonopotamus)
+* Avoid hang when using git hash-object --stdin --path #3902 (@bk2204)
+* synchronize access to netrcCredentialHelper.skip #3896 (@nataliechen1)
+
+### Misc
+
+* Improve license files #3973 (@bk2204)
+* Add CI link to CI badge in README #3960 (@slonopotamus)
+* Clarify output shown by `git lfs status` #3953 (@austintraver)
+* Revert "ci: force Windows Git version to 2.22.0" #3903 (@bk2204)
+* Better document pointer format constraints #3944 (@bk2204)
+* Don't abort with newer Git when in a bare repo #3940 (@bk2204)
+* Fix more Linux package issues #3932 (@bk2204)
+* docs: explain shell metacharacters better #3920 (@bk2204)
+* Reset the text attribute on export #3913 (@bk2204)
+* Support schannel ssl backend #3868 (@nikola-sh)
+* Allow migrate export to handle non-pointer files gracefully #3911 (@bk2204)
+* git/gitattr: fix dropped test errors #3904 (@alrs)
+* Accept all local references with git lfs push #3876 (@pluehne)
+* Drop pre-1.6 Go compatibility code #3897 (@slonopotamus)
+* tools/kv: Fix dropped test error #3882 (@alrs)
+* Use different parser for cookiejar files #3886 (@ssgelm)
+* Stop replacing files in LFS storage when downloading them concurrently on Windows #3880 (@slonopotamus)
+* Fix error strings to follow Go guidelines #3871 (@slonopotamus)
+* Miscellaneous release fixes #3866 (@bk2204)
+
+## 2.9.2 (12 December 2019)
+
+This release fixes a few regressions, such as a possible nil pointer
+dereference, a failure to retry batch requests, and a bug where repositories
+could fail to be detected on Windows.
+
+We would like to extend a special thanks to the following open-source
+contributors:
+
+* @exceed-alae for fixing a possible nil pointer dereference
+
+### Bugs
+
+* Add nil-check on defer block of DoTransfer() #3936 (@exceed-alae)
+* Retry batch failures #3930 (@bk2204)
+* rpm: use old setup code on CentOS 7 #3938 (@bk2204)
+* Handle missing cygpath gracefully #3910 (@bk2204)
+
+### Misc
+
+* Don't abort with newer Git when in a bare repo #3940 (@bk2204)
+* Fix more Linux package issues #3932 (@bk2204)
+
+## 2.9.1 (25 November 2019)
+
+This release fixes a few regressions, such as the ability to use HTTP/1.1 when
+required, addresses a race condition, and switches the cookie jar parser to
+something that's easier for distributions to package.
+
+We would like to extend a special thanks to the following open-source
+contributors:
+
+* @nataliechen1 for fixing a data race
+* @ssgelm for writing and updating the code to use a new cookie jar parser
+
+### Features
+
+* Allow specifying HTTP version to use #3887 (@bk2204)
+
+### Bugs
+
+* synchronize access to netrcCredentialHelper.skip #3896 (@nataliechen1)
+* Fix several causes of CI problems #3878 (@bk2204)
+* Miscellaneous release fixes #3866 (@bk2204)
+
+### Misc
+
+* Build artifacts during CI for easier testing #3892 (@bk2204)
+* Use different parser for cookiejar files #3886 (@ssgelm)
+
+## 2.9.0 (17 October 2019)
+
+This release adds support for DragonFly BSD, adds a new `git lfs dedup` command
+to save space if the file system supports it, adds support for file URLs,
+improves the performance when walking the repository, contains improvements
+to use HTTP/2 when available and cookies when required, and numerous other bug
+fixes, features, and modifications.
+
+We would like to extend a special thanks to the following open-source
+contributors:
+
+* @pluehne for adding support for fetching the history of specific refs
+* @kupson for adding cookie support
+* @liweitianux for adding Dragonfly BSD support
+* @kazuki-ma for implementing de-duplication support
+* @dvdveer for adding range support to ls-files
+* @dyrone, @pmeerw, @yamiacat, and @kittenking for cleaning up some documentation issues
+* @slonopotamus for improving concurrent downloads
+* @nataliechen1 for fixing remote names with dots
+* @jw3 for removing excessive logging
+* @SeamusConnor for significantly improving performance when walking the repository
+
+### Features
+
+* Support fetching entire history of specific refs #3849 (@pluehne)
+* Add support for CentOS 8 #3854 (@bk2204)
+* Let git-lfs HTTPS transport send cookies #3825 (@kupson)
+* Support DragonFly BSD #3837 (@liweitianux)
+* HTTP/2 protocol support #3793 (@PastelMobileSuit)
+* Add clonefile on Windows over ReFS support. #3790 (@kazuki-ma)
+* Add new command `git lfs dedup` for file system level de-duplication. #3753 (@kazuki-ma)
+* Support GIT_ALTERNATE_OBJECT_DIRECTORIES #3765 (@bk2204)
+* ls-files: add support for reference range #3764 (@dvdveer)
+* Add several additional distros for packagecloud.io #3751 (@bk2204)
+* Provide an option to track to handle paths literally #3756 (@bk2204)
+* Optimize traversal of Git objects with URL remotes #3755 (@bk2204)
+* Support for file URLs #3748 (@bk2204)
+* Add clone file on MacOS X (darwin). #3745 (@kazuki-ma)
+
+### Bugs
+
+* Fix JSON comma problems in docs #3851 (@dyrone)
+* Remove redundant comma in batch.md #3841 (@dyrone)
+* More robust handling of parallel attempts to download the same file #3826 (@slonopotamus)
+* Update wildmatch to v1.0.4 #3820 (@bk2204)
+* Update to gitobj v1.4.1 #3815 (@bk2204)
+* Fix build error when cross-compiling #3817 (@bk2204)
+* Do not fail when multiple processes download the same lfs file #3813 (@slonopotamus)
+* Fix Remote Name Parsing Bug #3812 (@nataliechen1)
+* status: gracefully handle files replaced by directories #3768 (@bk2204)
+* Avoid deadlock when transfer queue fails #3800 (@bk2204)
+* Avoid a hang when Git is slow to provide us data #3806 (@bk2204)
+* tasklog/log.go: print "done" messages with a trailing period #3789 (@ttaylorr)
+* track: make --filename work with spaces #3785 (@bk2204)
+* Fix couple of 'the the' typos #3786 (@pmeerw)
+* Use an absolute path for smudging #3780 (@bk2204)
+* Fix URL parsing with Go 1.12.8 #3771 (@bk2204)
+* Fix remote autoselection when not on a branch #3759 (@bk2204)
+* Replace deprecated SEEK_SET, SEEK_CUR usage. #3739 (@kazuki-ma)
+* Do not log skipped checkouts to file #3736 (@jw3)
+* Fix typos across git-lfs repository #3728 (@kittenking)
+* Accept legacy Git SSH URLs #3713 (@bk2204)
+
+### Misc
+
+* ls-files --all man patch #3859 (@yamiacat)
+* Reworked to use git ls-files in some circumstances instead of FastWalkGitRepo #3823 (@SeamusConnor)
+* Clean up go.mod for Go 1.13 #3807 (@bk2204)
+* Use FICLONE instead of BTRFS_IOC_CLONE. #3796 (@kazuki-ma)
+* Remove unused pty code #3737 (@bk2204)
+
+## 2.8.0 (23 July 2019)
+
+This release adds support for SOCKS proxies and Windows junctions, adds native
+packages for Debian 10 and similar distributions, reduces the number of
+situations in which running `git lfs fetch --all` is required, improves
+compatibility with Cygwin, and numerous other bug fixes and modifications.
+
+We would like to extend a special thanks to the following open-source
+contributors:
+
+* @mstrap for adding support for listing lock owners
+* @h-hirokawa for adding support for rewriting object URLs
+* @slonopotamus for helping get our specs and implementation in sync
+* @ssgelm for improving our Debian packaging
+* @TBK for fixing a test
+* @hartzell for improving the compatibility of our Makefile
+* @AJH16 for implementing support for NTLM SSO
+
+### Features
+
+* Don't fail if we lack objects the server has #3634 (@bk2204)
+* Add support for Debian 10 #3697 (@bk2204)
+* Migrate tags pointing to other tags #3690 (@bk2204)
+* Add support for SOCKS proxies #3677 (@bk2204)
+* Allow vendors to customize the version info #3636 (@bk2204)
+* Wrap credential data to allow late credential prompting and update NTLM/SSPI to attempt SSPI login prior to prompting for credentials. #3617 (@AJH16)
+* git-lfs locks should optionally denote own locks #3569 (@mstrap)
+* tq/adapterbase: support rewriting href #3590 (@h-hirokawa)
+* Handle Windows junctions properly #3560 (@bk2204)
+* Allow specifying multiple insteadOf aliases #3550 (@bk2204)
+
+### Bugs
+
+* Make API documentation lock creation example less confusing #3648 (@bk2204)
+* Use a download token when searching locks #3715 (@bk2204)
+* Copy mode from original file when rewriting objects #3694 (@bk2204)
+* Don't recurse into submodules when walking repository #3686 (@bk2204)
+* Be more precise about what timestamps we accept #3680 (@bk2204)
+* Canonicalize common directory paths on Cygwin #3671 (@bk2204)
+* Ensure we always use correct Content-Type and Accept headers #3663 (@bk2204)
+* Fix 'owner' lock field not documented as optional #3651 (@slonopotamus)
+* Improve error handling in git lfs install #3624 (@bk2204)
+* Properly handle config options for URLs with upper case letters #3584 (@bk2204)
+* Detect Cygwin-style pipe TTYs as TTYs #3582 (@bk2204)
+* Set push remote for pre-push #3579 (@bk2204)
+* Switch from manually running go generate to using dh-golang to run it #3549 (@ssgelm)
+* Install worktree hooks in the proper directory #3547 (@bk2204)
+* Avoid nil pointer dereference on download failure #3537 (@bk2204)
+* Avoid nil pointer dereference on unexpected failure #3534 (@bk2204)
+
+### Misc
+
+* Update gitobj to v1.3.1 #3716 (@bk2204)
+* Use default line endings for core.autocrlf=input #3712 (@bk2204)
+* Fix CircleCI #3710 (@bk2204)
+* Vendor in gitobj v1.3.0 #3685 (@bk2204)
+* Update CONTRIBUTING #3673 (@bk2204)
+* Fix typo in t-locks.sh #3666 (@TBK)
+* Make 'locked_at' required in JSON schema #3655 (@slonopotamus)
+* Document a new batch error code #3639 (@bk2204)
+* Fix invalid JSON in LFS locking API documentation #3650 (@slonopotamus)
+* Fix invalid JSON in locking protocol docs #3644 (@slonopotamus)
+* Various release updates #3623 (@bk2204)
+* tq/adapterbase: fix typo enableHrefRerite to enableHrefRewrite #3594 (@h-hirokawa)
+* Use git-lfs version of go-ntlm #3588 (@bk2204)
+* Log test server standard error to log file #3577 (@bk2204)
+* Don't set -extldflags unless LDFLAGS has a value #3545 (@hartzell)
+* Retry on oversize file #3518 (@bk2204)
+* Fix asset uploading during releases #3538 (@bk2204)
+
+## 2.7.0 (15 February 2019)
+
+This release adds better support for large files on 32-bit systems, adds
+attribute macros, fixes several file descriptor leaks, improves compatibility
+with Git's configuration parsing, and includes numerous other bug fixes and
+modifications.
+
+We would like to extend a special thanks to the following open-source
+contributors:
+
+* @andyneff and @torbjoernk for updating our release targets
+* @zkry for work on rate-limiting
+* @Foxboron for work on reproducible builds
+* @mstrap for adding a release target for Linux arm64
+* @keiko713, @Erwyn, and @mloskot for improving our documentation
+* @QuLogic for fixing our tests under SELinux
+* @saracen and @steffengodskesen for improving our output handling
+* @mbsulliv for finding and fixing a bug where we ran out of file descriptors
+
+### Features
+
+* Add sles 15 support #1055 #3515 (@andyneff)
+* docs/man/git-lfs-config.5.ronn: document GIT_LFS_SKIP_SMUDGE #3509 (@ttaylorr)
+* commands/command_pointer.go: introduce `--check` option #3501 (@ttaylorr)
+* Makefile additions for reproducible builds and asmflags #3444 (@Foxboron)
+* locking: add flag to control modification of ignored files #3409 (@bk2204)
+* build package for Ubuntu 18.10 aka Cosmic #3402 (@torbjoernk)
+* Add support for retries with delays (ex. rate limiting) #3449 (@zkry)
+* Trim embedded paths out of binaries #3443 (@bk2204)
+* Ensure 32-bit Git LFS binaries can handle files larger than 4 GiB #3426 (@bk2204)
+* Support attribute macros #3391 (@bk2204)
+* tasklog: don't log progress status when stdout is not a tty #3349 (@steffengodskesen)
+* locking: cache JSON response from server #3253 (@mstrap)
+* tq: enable transfer debugging when GIT_CURL_VERBOSE is set #3341 (@bk2204)
+
+### Bugs
+
+* .circleci: don't use 'brew prune' #3514 (@ttaylorr)
+* t/t-smudge.sh: remove unnecessary test #3513 (@ttaylorr)
+* docs/man: fix inconsistency in 'git-lfs-ls-files(1)' #3496 (@ttaylorr)
+* lfshttp: close body on redirect #3479 (@bk2204)
+* status: handle deleted files gracefully #3482 (@bk2204)
+* Fix hang in prune with too few file descriptors #3460 (@bk2204)
+* Fix parameter name on List Locks API Documentation #3477 (@Erwyn)
+* TST: Trim security context when checking permissions. #3476 (@QuLogic)
+* command/env: ensure we honor lfs.url #3470 (@bk2204)
+* Fix swapped case sensitivity in patterns #3433 (@bk2204)
+* core.sharedRepository improvements for directories #3417 (@bk2204)
+* Update the doc of whitelisted .lfsconfig keys #3423 (@keiko713)
+* Rewrite URL config-matching #3392 (@PastelMobileSuit)
+* git: close blob objects when finished #3379 (@bk2204)
+* Avoid hang in repos cloned with --shared or --reference #3383 (@bk2204)
+* commands/command_status.go: require a working copy #3378 (@ttaylorr)
+* Fix test server API #3377 (@bk2204)
+* vendor: don't remove necessary dependencies #3356 (@ttaylorr)
+* filepathfilter: don't say file is both accepted and rejected #3360 (@bk2204)
+* Support pushInsteadOf aliases when determining endpoints #3353 (@bk2204)
+* Close attributes file #3347 (@mbsulliv)
+* Fix humanize's FormatByteRate() to work with 0s duration #3340 (@saracen)
+
+### Misc
+
+* Release automation #3510 (@bk2204)
+* docs/man: update `git-lfs-fetch(1)` manpage #3488 (@ttaylorr)
+* Update Cobra #3483 (@bk2204)
+* Run go generate only on Windows #3480 (@bk2204)
+* docs/man/git-lfs-migrate: make examples less confusing #3424 (@bk2204)
+* Modify logic of 'migrate info' to process extensionless files #3458 (@zkry)
+* Improve error message on missing object #3398 (@bk2204)
+* docs/man: suggest using Git configuration for LFS keys #3394 (@bk2204)
+* Document default value of migrate info --top=<n> #3387 (@mloskot)
+* Clarify minimum git version #3327 (@carlwgeorge)
+
+## 2.6.1 (3 December 2018)
+
+This release contains miscellaneous bug fixes since v2.6.0. Most notably,
+release v2.6.1 restores support for alternate repositories, which was
+accidentally broken in v2.6.0.
+
+### Bugs
+
+* git: close blob objects when finished #3379 (@bk2204)
+* Avoid hang in repos cloned with --shared or --reference #3383 (@bk2204)
+* vendor: don't remove necessary dependencies #3356 (@ttaylorr)
+
+## 2.6.0 (1 November, 2018)
+
+This release adds better support for redirecting network calls from a Git LFS
+API server to one that requires a different authentication mode, builds Git LFS
+on Go 1.11, and numerous other bug fixes and modifications.
+
+We would like to extend a special thanks to the following open-source
+contributors:
+
+* @andyneff for updating our release targets
+* @gtsiolis: for removing the deprecated `git lfs clone` from the listing of
+  supported Git LFS commands
+* @jsantell for fixing a formatting issue in the INCLUDE AND EXCLUDE man page
+  section
+* @mmlb for adding a release target for Linux arm64
+* @skashyap7 for adding the 'git lfs track -n'
+* @Villemoes: for modernizing the Git LFS installation procedure on Debian.
+
+### Features
+
+* commands: list explicitly excluded patterns separately #3320 (@bk2204)
+* Uninstall improvements #3326 (@bk2204)
+* config: honor GIT_AUTHOR_DATE and GIT_COMMITTER_DATE #3314 (@bk2204)
+* Add new `.netrc` credential helper #3307 (@PastelMobileSuit)
+* Honor umask and core.sharedRepository #3304 (@bk2204)
+* Support listing only filename tracked by git lfs using --name (-n) option
+  #3271 (@skashyap7)
+* all: use Go 1.11.1 in CI #3298 (@ttaylorr)
+* lfsapi/tq: Have DoWithAuth() caller determine URL Access Mode #3293
+  (@PastelMobileSuit)
+* commands: undeprecate checkout #3303 (@bk2204)
+* Checkout options for conflicts #3296 (@bk2204)
+* Makefile: build source tarballs for release #3283 (@bk2204)
+* Encrypted SSL key support #3270 (@bk2204)
+* Add support for core.sshCommand #3235 (@bk2204)
+* gitobj-based Object Scanner #3236 (@bk2204)
+* README.md: new core team members #3217 (@ttaylorr)
+* Add build and releases for linux arm64 #3196 (@mmlb)
+* Update packagecloud.rb #3210 (@andyneff)
+* all: use Go modules instead of Glide #3208 (@ttaylorr)
+* all: use Go 1.11 in CI #3203 (@ttaylorr)
+
+### Bugs
+
+* Fix formatting of INCLUDE AND EXCLUDE (REFS) #3330 (@jsantell)
+* go.sum: add missing entries #3319 (@bk2204)
+* Ensure correct syntax for commit headers in lfs migrate import #3313 (@bk2204)
+* Clean up trailing whitespace #3299 (@bk2204)
+* commands: unambiguously resolve remote references #3285 (@ttaylorr)
+* Expand custom transfer args by using the shell #3259 (@bk2204)
+* Canonicalize paths properly on Windows #3277 (@bk2204)
+* debian/prerm: add --system flag #3272 (@Villemoes)
+* t: make testsuite run under git rebase -x #3262 (@bk2204)
+* git/gitattr: parse 'set' attributes #3255 (@ttaylorr)
+* t: avoid panic in lfstest-customadapter #3243 (@bk2204)
+* t: avoid using shell variables in printf's first argument #3242 (@bk2204)
+* lfsapi: handle SSH hostnames and aliases without users #3230 (@bk2204)
+* commands/command_ls_files.go: ignore index with argument #3219 (@ttaylorr)
+* commands/command_migrate_import.go: install hooks #3227 (@ttaylorr)
+* t: mark test sources as .PHONY #3228 (@ttaylorr)
+* Pass GIT_SSH_COMMAND to the shell #3199 (@bk2204)
+* Tidy misformatted files #3202 (@bk2204)
+* config: expand core.hooksPath #3212 (@ttaylorr)
+* locks: manage write permissions of ignored files #3190 (@ttaylorr)
+
+### Misc
+
+* CONTRIBUTING.md: :nail_care: #3325 (@ttaylorr)
+* Update CONTRIBUTING #3317 (@bk2204)
+* go.mod: depend on tagged gitobj #3311 (@ttaylorr)
+* RFC: SSH protocol #3290 (@bk2204)
+* Remove `git lfs clone` command from man #3301 (@gtsiolis)
+* ROADMAP.md: use GitHub issues instead #3286 (@ttaylorr)
+* docs: add note about closing release milestone #3274 (@bk2204)
+* CI improvements #3268 (@bk2204)
+* docs/howto: document our release process #3261 (@ttaylorr)
+* Create new lfshttp package #3244 (@PastelMobileSuit)
+* CONTRIBUTING: update required go version #3232 (@PastelMobileSuit)
+* go.mod: use latest github.com/olekukonko/ts #3223 (@ttaylorr)
+* go.mod: pin github.com/git-lfs/wildmatch to v1.0.0 #3218 (@ttaylorr)
+* Update README.md #3193 (@srl295)
+
+## 2.5.2 (17 September, 2018)
+
+### Bugs
+
+* config: Treat [host:port]:path URLs correctly #3226 (@saschpe)
+* tq: Always provide a Content-Type when uploading files #3201 (@bk2204)
+* commands/track: Properly `lfs track` files with escaped characters in their
+  name #3192 (@leonid-s-usov)
+
+### Misc
+
+* packagecloud.rb: remove older versions #3210 (@andyneff)
+
+## 2.5.1 (2 August, 2018)
+
+This release contains miscellaneous bug fixes since v2.5.0. Most notably,
+release v2.5.1 allows a user to disable automatic Content-Type detection
+(released in v2.5.0) via `git config lfs.contenttype false` for hosts that do
+not support it.
+
+### Features
+
+* tq: make Content-Type detection disable-able #3163 (@ttaylorr)
+
+### Bugs
+
+* Makefile: add explicit rule for commands/mancontent_gen.go #3160 (@jj1bdx)
+* script/install.sh: mark as executable #3155 (@ttaylorr)
+* config: add origin to remote list #3152 (@PastelMobileSuit)
+
+### Misc
+
+* docs/man/mangen.go: don't show non-fatal output without --verbose #3168
+  (@ttaylorr)
+* LICENSE.md: update copyright year #3156 (@IMJ355)
+* Makefile: silence some output #3164 (@ttaylorr)
+* Makefile: list prerequisites for resource.syso #3153 (@ttaylorr)
+
+## 2.5.0 (26 July, 2018)
+
+This release adds three new migration modes, updated developer ergonomics, and
+a handful of bug fixes to Git LFS.
+
+We would like to extend a special thanks to the following open-source
+contributors:
+
+* @calavera for fixing a broken Go test and adding support for custom
+  Content-Type headers in #3137 and #3138.
+* @cbuehlmann for adding support for encoded character names in filepaths via
+  #3093.
+* @larsxschneider for changing the default value of lfs.allowincompletepush in
+  #3109.
+* @NoEffex for supporting TTL in SSH-based authentication tokens via #2867.
+* @ssgelm for adding 'go generate' to our Debian packages via #3083.
+
+### Features
+
+* Makefile: replace many scripts with make targets #3144 (@ttaylorr)
+* {.travis,appveyor}.yml: upgrade to Go 1.10.3 #3146 (@ttaylorr)
+* t: run tests using prove #3125 (@ttaylorr)
+* commands/migrate: infer wildmatches with --fixup #3114 (@ttaylorr)
+* Retry SSH resolution 5 times #2934 (@stanhu)
+* Implement `migrate export` subcommand #3084 (@PastelMobileSuit)
+* Add `--no-rewrite` flag to `migrate import` command #3029 (@PastelMobileSuit)
+
+### Bugs
+
+* t: fix contains_same_elements() fn #3145 (@PastelMobileSuit)
+* commands: warn if working copy is dirty #3124 (@ttaylorr)
+* Ensure provided remote takes precedence over configured pushRemote #3139 (@PastelMobileSuit)
+* Fix proxy unit tests. #3138 (@calavera)
+* commands/command_migrate.go: loosen meaning of '--everything' #3121 (@ttaylorr)
+* lfsapi: don't query askpass for given creds #3126 (@PastelMobileSuit)
+* config/git_fetcher.go: mark 'lfs.allowincompletepush' as safe #3113 (@ttaylorr)
+* fs: support multiple object alternates #3116 (@ttaylorr)
+* commands/checkout: checkout over read-only files #3120 (@ttaylorr)
+* test/testhelpers.sh: look for 64 character SHA-256's #3119 (@ttaylorr)
+* config/config.go: case-insensitive error search #3098 (@ttaylorr)
+* Encoded characters in pathnames #3093 (@cbuehlmann)
+* Support default TTL for authentication tokens acquired via SSH #2867 (@NoEffex)
+* commands/status.go: relative paths outside of root #3080 (@ttaylorr)
+* Run `go generate` on commands in deb build #3083 (@ssgelm)
+* lfsapi: prefer proxying from gitconfig before environment #3062 (@ttaylorr)
+* commands/track: respect global- and system-level gitattributes #3076 (@ttaylorr)
+* git/git.go: pass --multiple to git-fetch(1) when appropriate #3063 (@ttaylorr)
+* commands/checkout: fix inaccurate messaging #3055 (@ttaylorr)
+* commands/migrate: do not migrate empty commits #3054 (@ttaylorr)
+* git/odb: retain trailing newlines in commit messages #3053 (@ttaylorr)
+
+### Misc
+
+* Set original file content type on basic upload. #3137 (@calavera)
+* README.md: Git for Windows ships LFS by default #3112 (@larsxschneider)
+* change lfs.allowincompletepush default from true to false  #3109 (@larsxschneider)
+* *: replace git/odb with vendored copy #3108 (@ttaylorr)
+* test/test-ls-files.sh: skip on CircleCI #3101 (@ttaylorr)
+* lfsapi/ssh.go: use zero-value sentinels #3099 (@ttaylorr)
+* README.md: add link to installation wiki page #3075 (@ttaylorr)
+* docs/man/git-lfs.1.ronn: update casing and missing commands #3059 (@ttaylorr)
+* commands/checkout: mark 'git lfs checkout' as deprecated #3056 (@ttaylorr)
+
+## 2.4.2 (28 May, 2018)
+
+### Bugs
+
+* lfsapi: re-authenticate HTTP redirects when needed #3028 (@ttaylorr)
+* lfsapi: allow unknown keywords in netrc file(s) #3027 (@ttaylorr)
+
+## 2.4.1 (18 May, 2018)
+
+This release fixes a handful of bugs found and fixed since v2.4.0. In
+particular, Git LFS no longer panic()'s after invalid API responses, can
+correctly run 'fetch' on SHAs instead of references, migrates symbolic links
+correctly, and avoids writing to `$HOME/.gitconfig` more than is necessary.
+
+We would like to extend a "thank you" to the following contributors for their
+gracious patches:
+
+- @QuLogic fixed an issue with running tests that require credentials
+- @patrickmarlier made it possible for 'git lfs migrate import' to work
+  correctly with symbolic links.
+- @zackse fixed an inconsistency in `CONTRIBUTING.md`
+- @zanglang fixed an inconsistency in `README.md`
+
+Git LFS would not be possible without generous contributions from the
+open-source community. For these, and many more: thank you!
+
+### Features
+
+* script/packagecloud.rb: release on Ubuntu Bionic #2961 (@ttaylorr)
+
+### Bugs
+
+* lfsapi: canonicalize extra HTTP headers #3010 (@ttaylorr)
+* commands/lock: follow symlinks before locking #2996 (@ttaylorr)
+* lfs/attribute.go: remove default value from upgradeables #2994 (@ttaylorr)
+* git: include SHA1 in ref-less revisions #2982 (@ttaylorr)
+* Do not migrate the symlinks to LFS objects. #2983 (@patrickmarlier)
+* commands/uninstall: do not log about global hooks with --local #2976 (@ttaylorr)
+* commands/run.go: exit 127 on unknown sub-command #2969 (@ttaylorr)
+* commands/{un,}track: perform "prefix-agnostic" comparisons #2955 (@ttaylorr)
+* commands/migrate: escape paths before .gitattributes  #2933 (@ttaylorr)
+* commands/ls-files: do not accept '--all' after '--' #2932 (@ttaylorr)
+* tq: prevent uint64 underflow with invalid API response #2902 (@ttaylorr)
+
+### Misc
+
+* test/test-env: skip comparing GIT_EXEC_PATH #3015 (@ttaylorr)
+* remove reference to CLA from contributor's guide #2997 (@zackse)
+* .gitattributes link is broken #2985 (@zanglang)
+* commands: make --version a synonym for 'version' #2968, #3017 (@ttaylorr)
+* test: ensure that git-mergetool(1) works with large files #2939 (@ttaylorr)
+* README.md: note the correct PackageCloud URL #2960 (@ttaylorr)
+* README.md: mention note about `git lfs track` retroactively #2948 (@ttaylorr)
+* README.md: reorganize into Core Team, Alumni #2941 (@ttaylorr)
+* README.md: :nail_care: #2942 (@ttaylorr)
+* circle.yml: upgrade to 'version: 2' syntax #2928 (@ttaylorr)
+* Use unique repo name for tests that require credentials. #2901 (@QuLogic)
+
+## 2.4.0 (2 March, 2018)
+
+This release introduces a rewrite of the underlying file matching engine,
+expands the API to include relevant refspecs for individual requests,
+standardizes the progress output among commands, and more.
+
+Please note: in the next MAJOR release (v3.0.0) the semantic meaning behind
+`--include` and `--exclude` flags will change. As the details of exactly which
+existing patterns will no longer function as previously are known, we will
+indicate them here. Any `--include` or `--exclude` patterns used in v2.3.0 or
+earlier are expected to work as previously in this release.
+
+This release would not be possible without the open-source community.
+Specifically, we would like to thank:
+
+- @larsxschneider: for contributing fixes to the filter operation in `git lfs
+  fsck`, and `git lfs prune`, as well as the bug report leading to the
+  filepathfilter changes.
+- @yfronto: for adding new Linux release targets.
+- @stffabi: for adding support for NTLM with SSPI on Windows.
+- @jeffreydwalter: for fixing memory alignment issues with `sync/atomic` on
+  32-bit architectures.
+- @b4mboo: for adding a LFS configuration key to the list of safe configuration
+  options.
+
+Without the aforementioned indviduals, this release would not have been
+possible. Thank you!
+
+### Features
+
+* __Support wildmatch-compliant options in `--include`, `--exclude`__
+  * filepathfilter: implement using wildmatch #2875 (@ttaylorr)
+  * test: add wildmatch migration tests #2888 (@larsxschneider, @ttaylorr)
+* __Expand the specification to include relevant refspecs__
+  * verify locks against each ref being pushed #2706 (@technoweenie)
+  * Batch send refspec take 2 #2809 (@technoweenie)
+  * Run 1 TransferQueue per uploaded ref #2806 (@technoweenie)
+  * Locks/verify: full refspec #2722 (@technoweenie)
+  * send remote refspec for the other lock commands #2773 (@technoweenie)
+* __Standardize progress meter output and implementation__
+  * tq: standardized progress meter formatting #2811 (@ttaylorr)
+  * commands/fetch: unify formatting #2758 (@ttaylorr)
+  * commands/prune: unify formatting #2757 (@ttaylorr)
+  * progress: use git/githistory/log package for formatting #2732 (@ttaylorr)
+  * progress: remove `*progress.Meter` #2762 (@ttaylorr)
+  * tasklog: teach `*Logger` how to enqueue new `*SimpleTask`'s #2767 (@ttaylorr)
+  * progress: remove spinner.go #2759 (@ttaylorr)
+* __Teach new flags, functionality to `git lfs ls-files`__
+  * commands: teach '--all' to `git lfs ls-files` #2796 (@ttaylorr)
+  * commands/ls-files: show cached, tree-less LFS objects #2795 (@ttaylorr)
+  * commands/ls-files: add --include, --exclude #2793 (@ttaylorr)
+  * commands/ls-files: add '--size' flag #2764 (@ttaylorr)
+* __Add new flags, functionality to `git lfs migrate`__
+  * commands/migrate: support '^'-prefix refspec in arguments #2785 (@ttaylorr)
+  * commands/migrate: add '--skip-fetch' for offline migrations #2738 (@ttaylorr)
+  * git: prefer sending revisions over STDIN than arguments #2739 (@ttaylorr)
+* __Release to new operating systems__
+  * release lfs for ubuntu/artful too #2704 (@technoweenie)
+  * Adding Mint Sylvia to packagecloud.rb script #2829 (@yfronto)
+* __New functionality in package `lfsapi`__
+  * NTLM authentication with SSPI on windows #2871 (@stffabi)
+  * lfsapi/auth: teach DoWithAuth to respect http.extraHeaders #2733 (@ttaylorr)
+  * add support for url-specific proxies #2651 (@technoweenie)
+* __Code cleanup in git.Config, package `localstorage`__
+  * Tracked remote #2700 (@technoweenie)
+  * Replace git.Config #2692 (@technoweenie)
+  * Replace localstorage #2689 (@technoweenie)
+  * Remove last global config #2687 (@technoweenie)
+  * Git config refactor #2676 (@technoweenie)
+
+### Bugs
+
+* all: fix 32-bit alignment issues with `sync/atomic` #2883 (@ttaylorr)
+* all: memory alignment issues on 32-bit systems. #2880 (@jeffreydwalter)
+* command/migrate: don't migrate remote references in bare repositories #2769 (@ttaylorr)
+* commands/ls-files: behave correctly before initial commit #2794 (@ttaylorr)
+* commands/migrate: allow for ambiguous references in migrations #2734 (@ttaylorr)
+* commands: fill in missing printf arg #2678 (@technoweenie)
+* config: Add `lfs.locksverify` to safe keys. #2797 (@b4mboo)
+* don't replace pointers with objects if clean filter is not configured #2626 (@technoweenie)
+* fsck: attach a filter to exclude unfetched items from fsck #2847 (@larsxschneider)
+* git/githistory: copy entries from cache, elsewhere #2884 (@ttaylorr)
+* git/githistory: migrate annotated tags correctly #2780 (@ttaylorr)
+* git/odb: don't print extra newline after commit message #2784 (@ttaylorr)
+* git/odb: extract identifiers from commits verbatim #2751 (@wsprent)
+* git/odb: implement parsing for annotated `*Tag`'s #2778 (@ttaylorr)
+* git/odb: retain newlines when parsing commit messages #2786 (@ttaylorr)
+* lfs: PointerScanner is nil after error, so don't close #2699 (@technoweenie)
+* lfsapi: Cred helper improvements #2695 (@technoweenie)
+* lfsapi: retry requests changing access from none IF Auth header is empty #2621 (@technoweenie)
+* prune: always prune excluded paths #2851 (@larsxschneider)
+* status: fix incorrect formatting with unpushed objects #2746 (@ttaylorr)
+* tasklog: don't drop updates in PercentageTask #2755 (@ttaylorr)
+* test: Fix integration test early exit #2735 (@technoweenie)
+* test: generate random repo names with fs-safe characters #2698 (@technoweenie)
+
+### Misc
+
+* all: Nitpicks #2821 (@technoweenie)
+* all: introduce package 'tlog' #2747 (@ttaylorr)
+* all: remove CLA #2870 (@MikeMcQuaid)
+* build: Specify the embedded Windows icon as part of versioninfo.json #2770 (@sschuberth)
+* config,test: Testlib no global config #2709 (@mathstuf)
+* config: add PushRemote() for checking `branch.*.pushRemote` and `remote.pushDefault` first #2715 (@technoweenie)
+* docs: Added documentation for git-lfs-ls-files' `*/-` output. #2719 (@bilke)
+* docs: Uninstall man page improvements #2730 (@dpursehouse)
+* docs: Update usage info for post-checkout #2830 (@proinsias)
+* docs: add 'git lfs prune' to main man page #2849 (@larsxschneider)
+* docs: use consistent casing for Git #2850 (@larsxschneider)
+* git/githistory: have `*RefUpdater` hold `*odb.ObjectDatabase` reference #2779 (@ttaylorr)
+* progress: move CopyCallback (& related) to package 'tools' #2749 (@ttaylorr)
+* progress: move `*progressLogger` implementation to package 'tools' #2750 (@ttaylorr)
+* refspec docs #2820 (@technoweenie)
+* script/test: run 'go tool vet' during testing #2788 (@ttaylorr)
+* tasklog: introduce `*SimpleTask` #2756 (@ttaylorr)
+* test: Ignore comment attr lines #2708 (@mathstuf)
+* test: Wait longer for test lfs server to start. #2716 (@QuLogic)
+* test: ensure commented attr lines are ignored #2736 (@ttaylorr)
+* tools/humanize: add 'FormatByteRate' to format transfer speed #2810 (@ttaylorr)
+* vendor: update 'xeipuuv/gojsonpointer' #2846 (@ttaylorr)
+
+## 2.3.4 (18 October, 2017)
+
+### Features
+
+* 'git lfs install' updates filters with 'skip-smudge' option #2673 (@technoweenie)
+
+### Bugs
+
+* FastWalkGitRepo: limit number of concurrent goroutines #2672 (@technoweenie)
+* handle scenario where multiple configuration values exist in ~/.gitconfig #2659 (@shiftkey)
+
+## 2.3.3 (9 October, 2017)
+
+### Bugs
+
+* invoke lfs for 'git update-index', fixing 'status' issues #2647 (@technoweenie)
+* cache http credential helper output by default #2648 (@technoweenie)
+
+## 2.3.2 (3 October, 2017)
+
+### Features
+
+* bump default activity timeout from 10s -> 30s #2632 (@technoweenie)
+
+### Bugs
+
+* ensure files are marked readonly after unlocking by ID #2642 (@technoweenie)
+* add files to index with path relative to current dir #2641 (@technoweenie)
+* better Netrc errors #2633 (@technoweenie)
+* only use askpass if credential.helper is not configured #2637 (@technoweenie)
+* convert backslash to slash when writing to .gitattributes #2625 (@technoweenie)
+
+### Misc
+
+* only copy req headers if there are git-configured extra headers #2622 (@technoweenie)
+* update tracerx to add timestamps #2620 (@rubyist)
+
+## 2.3.1 (27 September, 2017)
+
+### Features
+
+* add support for SSH_ASKPASS #2609 (@technoweenie)
+* `git lfs migrate --verbose` option #2610 (@technoweenie)
+* Support standalone custom transfer based on API URL prefix match #2590 (@sprohaska)
+
+### Bugs
+
+* Improve invalid URL error messages #2614 (@technoweenie)
+* Fix double counting progress bug #2608 (@technoweenie)
+* trim whitespace from GIT_ASKPASS provided passwords #2607 (@technoweenie)
+* remove mmap usage in Packfile reader #2600 (@technoweenie)
+* `git lfs clone`: don't fetch for unborn repositories #2598 (@shiftkey)
+
+### Misc
+
+* Windows Installer fixes:
+  * Show proper icon in add/remove programs list #2585 (@shiftkey)
+  * Make the Inno Setup installer script explicitly check for the binaries #2588 (@sschuberth)
+  * Improve compile-win-installer-unsigned.bat a bit #2586 (@sschuberth)
+* Update migrate docs example for multiple file types #2596 (@technoweenie)
+
+## 2.3.0 (14 September, 2017)
+
+Git LFS v2.3.0 includes performance optimizations for the `git-lfs-migrate(1)`
+and `git-clone(1)` commands, new features, bug-fixes, and more.
+
+This release was made possible by contributors to Git LFS. Specifically:
+
+- @aleb: added support for "standalone" transfer agents, for using `rsync(1)`
+  and similar with Git LFS.
+- @bozaro: added support for custom `.git/lfs/objects` directories via the
+  `lfs.storage` configuration option.
+- @larsxschneider: fixed a recursive process leak when shelling out to Git,
+  added new features to `git lfs ls-files`, extra information in error
+  messages used for debugging, documentation changes and more.
+- @mathstuf: contributed a documentation change clarifying LFS's handling of
+  empty pointer files.
+- @rudineirk and @andyneff: updated our release process to build packages for
+  fedora/26.
+- @ssgelm: ensured that LFS is able to be released on Ubuntu Universe.
+
+To everyone who has contributed to this or previous releases of Git LFS: Thank
+you!
+
+### Features
+
+* git/odb/pack: improve `git lfs migrate` performance
+  * git/odb/pack: introduce packed object reassembly #2550 #2551 #2552 #2553 #2554 (@ttaylorr)
+  * git/odb/pack: teach packfile index entry lookups #2420 #2421 #2422 #2423 #2437 #2441 #2461 (@ttaylorr)
+  * git/{odb,githistory}: don't write unchanged objects #2541 (@ttaylorr)
+* commands: improve `git clone` performance with 'delay' capability #2511 #2469 #2468 #2471 #2467 #2476 #2483 (@ttaylorr)
+  * commands: mark `git lfs clone` as deprecated #2526 (@ttaylorr)
+* commands: enable `lfs.allowincompletepush` by default #2574 (@technoweenie)
+* commands: teach '--everything' to `git lfs migrate` #2558 (@ttaylorr)
+* commands: teach `git lfs ls-files` a '--debug' option #2540 (@larsxschneider)
+* commands,lfs: warn on 4gb size conversion during clean #2510 #2507 #2459 (@ttaylorr)
+* lfsapi/creds: teach about GIT_ASKPASS and core.askpass #2500 #2578 (@ttaylorr)
+* commands/status: indicate missing objects #2438 (@ttaylorr)
+* Allow using custom transfer agents directly #2429 (@aleb)
+* Add `lfs.storage` parameter for overriding LFS storage location #2023 (@bozaro)
+* lfsapi: enable credential caching by default #2508 (@ttaylorr)
+* commands/install: teach `--manual` to `git-lfs-install(1)` #2410 (@ttaylorr)
+
+### Bugs
+
+* migrate: fix migrations with subdirectories in '--include' or '--exclude' #2485 (@ttaylorr)
+* commands/migrate: fix hardlinking issue when different filesystem is mounted at `/tmp` #2566 (@ttaylorr)
+* commands: make `git lfs migrate` fetch ref updates before migrating #2538 (@ttaylorr)
+* commands: remove '--above=1mb' default from `git lfs migrate info` #2460 (@ttaylorr)
+* filepathfilter: fix `HasPrefix()` when no '--include' filters present #2579 (@technoweenie)
+* git/githistory/log: fix race condition with `git/githistory/log` tests #2495 (@ttaylorr)
+* git/odb: fix closing object database test #2457 (@ttaylorr)
+* git/githistory: only update local refs after migrations #2559 (@ttaylorr)
+* locking: fix unlocking files not removing write flag #2514 (@ttaylorr)
+* locks: fix unlocking files in a symlinked directory #2505 (@ttaylorr)
+* commands: teach `git lfs unlock` to ignore status errs in appropriate conditions #2475 (@ttaylorr)
+* git: expand `GetAttributePaths` check to include non-LFS lockables #2528 (@ttaylorr)
+* fix multiple `git update-index` invocations #2531 (@larsxschneider)
+* tools: fix SSH credential cacher expiration #2530 (@ttaylorr)
+* lfsapi: fix read/write race condition in credential cacher #2493 (@ttaylorr)
+* lfs: fix cleaning contents larger than 1024 bytes over stdin #2488 (@ttaylorr)
+* fsck only scans current version of objects #2049 (@TheJare)
+* progress: fix writing updates to `$GIT_LFS_PROGRESS` #2465 (@ttaylorr)
+* commands/track: resolve symlinks before comparing attr paths #2463 (@ttaylorr)
+* test: ensure that empty pointers are empty #2458 (@ttaylorr)
+* git/githistory/log: prevent 'NaN' showing up in `*PercentageTask` #2455 (@ttaylorr)
+* tq: teach Batch() API to retry itself after io.EOF's #2516 (@ttaylorr)
+
+### Misc
+
+* script/packagecloud: release LFS on Fedora/26 #2443 #2509 (@rudineirk, @andyneff)
+* git/githistory: change "Rewriting commits" when not updating refs #2577 (@ttaylorr)
+* commands: print IP addresses in error logs #2570 (@larsxschneider)
+* commands: print current time in UTC to error logs #2571 (@larsxschneider)
+* commands: Disable lock verification when using a standalone custom-tr… #2499 (@aleb)
+* docs/man: update `git lfs migrate` documentation with EXAMPLES #2580 (@technoweenie)
+* docs/man: recommend global per-host locking config #2546 (@larsxschneider)
+* commands: use transfer queue's batch size instead of constant #2529 (@ttaylorr)
+* add function to invoke Git with disabled LFS filters #2453 (@larsxschneider)
+* config: warn on unsafe keys in `.lfsconfig` #2502 (@ttaylorr)
+* glide: remove unused dependencies #2501 (@ttaylorr)
+* script/build: pass '-{ld,gc}flags' to compiler, if given #2462 (@ttaylorr)
+* spec: mention that an empty file is its own LFS pointer #2449 (@mathstuf)
+* Update to latest version of github.com/pkg/errors #2426 (@ssgelm)
+* Update gitignore to add some temp files that get created when building debs #2425 (@ssgelm)
+* lfs: indent contents of `git lfs install`, `update` #2392 (@ttaylorr)
+* tq: increase default `lfs.concurrenttransfers` to 8 #2506 (@ttaylorr)
+
+## 2.2.1 (10 July, 2017)
+
+### Bugs
+
+* git lfs status --json only includes lfs files #2374 (@asottile)
+* git/odb: remove temporary files after migration #2388 (@ttaylorr)
+* git/githistory: fix hanging on empty set of commits #2383 (@ttaylorr)
+* migrate: don't checkout HEAD on bare repositories #2389 (@ttaylorr)
+* git/odb: prevent cross-volume link error when saving objects #2382 (@ttaylorr)
+* commands: only pass --jobs to `git clone` if set #2369 (@technoweenie)
+
+### Misc
+
+* lfs: trace hook install, uninstall, upgrade #2393 (@ttaylorr)
+* vendor: remove github.com/cheggaaa/pb #2386 (@ttaylorr)
+* Use FormatBytes from git-lfs/tools/humanize instead of cheggaaa/pb #2377 (@ssgelm)
+
+
+## 2.2.0 (27 June, 2017)
+
+Git LFS v2.2.0 includes bug fixes, minor features, and a brand new `migrate`
+command. The `migrate` command rewrites commits, converting large files from
+Git blobs to LFS objects. The most common use case will fix a git push rejected
+for having large blobs:
+
+```
+$ git push origin master
+# ...
+remote: error: file a.psd is 1.2 gb; this exceeds github's file size limit of 100.00 mb
+to github.com:ttaylorr/demo.git
+ ! [remote rejected] master -> master (pre-receive hook declined)
+error: failed to push some refs to 'git@github.com:ttaylorr/demo.git'
+
+$ git lfs migrate info
+*.psd   1.2 GB   27/27 files(s)  100%
+
+$ git lfs migrate import --include="*.psd"
+migrate: Sorting commits: ..., done
+migrate: Rewriting commits: 100% (810/810), done
+  master        f18bb746d44e8ea5065fc779bb1acdf3cdae7ed8 -> 35b0fe0a7bf3ae6952ec9584895a7fb6ebcd498b
+migrate: Updating refs: ..., done
+
+$ git push origin
+Git LFS: (1 of 1 files) 1.2 GB / 1.2 GB
+# ...
+To github.com:ttaylorr/demo.git
+ * [new branch]      master -> master
+```
+
+The `migrate` command has detailed options described in the `git-lfs-migrate(1)`
+man page. Keep in mind that this is the first pass at such a command, so we
+expect there to be bugs and performance issues (especially on long git histories).
+Future updates to the command will be focused on improvements to allow full
+LFS transitions on large repositories.
+
+### Features
+
+* commands: add git-lfs-migrate(1) 'import' subcommand #2353 (@ttaylorr)
+* commands: add git-lfs-migrate(1) 'info' subcommand #2313 (@ttaylorr)
+* Implement status --json #2311 (@asottile)
+* commands/uploader: allow incomplete pushes #2199 (@ttaylorr)
+
+### Bugs
+
+* Retry on timeout or temporary errors #2312 (@jakub-m)
+* commands/uploader: don't verify locks if verification is disabled #2278 (@ttaylorr)
+* Fix tools.TranslateCygwinPath() on MSYS #2277 (@raleksandar)
+* commands/clone: add new flags since Git 2.9 #2251, #2252 (@ttaylorr)
+* Make pull return non-zero error code when some downloads failed #2237 (@seth2810)
+* tq/basic_download: guard against nil HTTP response #2227 (@ttaylorr)
+* Bugfix: cannot push to scp style URL #2198 (@jiangxin)
+* support lfs.<url>.* values where url does not include .git #2192 (@technoweenie)
+* commands: fix logged error not interpolating format qualifiers #2228 (@ttaylorr)
+* commands/help: print helptext to stdout for consistency with Git #2210 (@ttaylorr)
+
+### Misc
+
+* Minor cleanups in help index #2248 (@dpursehouse)
+* Add git-lfs-lock and git-lfs-unlock to help index #2232 (@dpursehouse)
+* packagecloud: add Debian 9 entry to formatted list #2211 (@ttaylorr)
+* Update Xenial is to use stretch packages #2212 (@andyneff)
+
+## 2.1.1 (19 May, 2017)
+
+Git LFS v2.1.1 ships with bug fixes and a security patch fixing a remote code
+execution vulnerability exploitable by setting a SSH remote via your
+repository's `.lfsconfig` to contain the string "-oProxyCommand". This
+vulnerability is only exploitable if an attacker has write access to your
+repository, or you clone a repository with a `.lfsconfig` file containing that
+string.
+
+### Bugs
+
+* Make pull return non-zero error code when some downloads failed #2245 (@seth2810, @technoweenie)
+* lfsapi: support cross-scheme redirection #2243 (@ttaylorr)
+* sanitize ssh options parsed from ssh:// url #2242 (@technoweenie)
+* filepathfilter: interpret as .gitignore syntax #2238 (@technoweenie)
+* tq/basic_download: guard against nil HTTP response #2229 (@ttaylorr)
+* commands: fix logged error not interpolating format qualifiers #2230 (@ttaylorr)
+
+### Misc
+
+* release: backport Debian 9-related changes #2244 (@ssgelm, @andyneff, @ttaylorr)
+* Add git-lfs-lock and git-lfs-unlock to help index #2240 (@dpursehouse)
+* config: allow multiple environments when calling config.Unmarshal #2224 (@ttaylorr)
+
+## 2.1.0 (28 April, 2017)
+
+### Features
+
+* commands/track: teach --no-modify-attrs #2175 (@ttaylorr)
+* commands/status: add blob info to each entry #2070 (@ttaylorr)
+* lfsapi: improve HTTP request/response stats #2184 (@technoweenie)
+* all: support URL-style configuration lookups (@ttaylorr)
+  * commands: support URL-style lookups for `lfs.{url}.locksverify` #2162 (@ttaylorr)
+  * lfsapi: support URL-style lookups for `lfs.{url}.access` #2161 (@ttaylorr)
+  * lfsapi/certs: use `*config.URLConfig` to do per-host config lookup #2160 (@ttaylorr)
+  * lfsapi: support for http.<url>.extraHeader #2159 (@ttaylorr)
+  * config: add prefix to URLConfig type #2158 (@ttaylorr)
+  * config: remove dependency on lfsapi package #2156 (@ttaylorr)
+  * config: support multi-value lookup on URLConfig #2154 (@ttaylorr)
+  * lfsapi: initial httpconfig type #1912 (@technoweenie, @ttaylorr)
+* lfsapi,tq: relative expiration support #2130 (@ttaylorr)
+
+### Bugs
+
+* commands: include error in `LoggedError()` #2179 (@ttaylorr)
+* commands: cross-platform log formatting to files #2178 (@ttaylorr)
+* locks: cross-platform path normalization #2139 (@ttaylorr)
+* commands,locking: don't disable locking for auth errors during verify #2110 (@ttaylorr)
+* commands/status: show partially staged files twice #2067 (@ttaylorr)
+
+### Misc
+
+* all: build on Go 1.8.1 #2145 (@ttaylorr)
+* Polish custom-transfers.md #2171 (@sprohaska)
+* commands/push: Fix typo in comment #2170 (@sprohaska)
+* config: support multi-valued config entries #2152 (@ttaylorr)
+* smudge: use localstorage temp directory, not system #2140 (@ttaylorr)
+* locking: send locks limit to server #2107 (@ttaylorr)
+* lfs: extract `DiffIndexScanner` #2035 (@ttaylorr)
+* status: use DiffIndexScanner to populate results #2042 (@ttaylorr)
+
+## 2.0.2 (29 March, 2017)
+
+### Features
+
+* ssh auth and credential helper caching #2094 (@ttaylorr)
+* commands,tq: specialized logging for missing/corrupt objects #2085 (@ttaylorr)
+* commands/clone: install repo-level hooks after `git lfs clone` #2074
+* (@ttaylorr)
+* debian: Support building on armhf and arm64 #2089 (@p12tic)
+
+### Bugs
+
+* commands,locking: don't disable locking for auth errors during verify #2111
+* (@ttaylorr)
+* commands: show real error while cleaning #2096 (@ttaylorr)
+* lfsapi/auth: optionally prepend an empty scheme to Git remote URLs #2092
+* (@ttaylorr)
+* tq/verify: authenticate verify requests if required #2084 (@ttaylorr)
+* commands/{,un}track: correctly escape '#' and ' ' characters #2079 (@ttaylorr)
+* tq: use initialized lfsapi.Client instances in transfer adapters #2048
+* (@ttaylorr)
+
+### Misc
+
+* locking: send locks limit to server #2109 (@ttaylorr)
+* docs: update configuration documentation #2097 #2019 #2102 (@terrorobe)
+* docs: update locking API documentation #2099 #2101 (@dpursehouse)
+* fixed table markdown in README.md #2095 (@ZaninAndrea)
+* remove the the duplicate work #2098 (@grimreaper)
+
+## 2.0.1 (6 March, 2017)
+
+### Misc
+
+* tq: fallback to `_links` if present #2007 (@ttaylorr)
+
+## 2.0.0 (1 March, 2017)
+
+Git LFS v2.0.0 brings a number of important bug fixes, some new features, and
+a lot of internal refactoring. It also completely removes old APIs that were
+deprecated in Git LFS v0.6.
+
+### Locking
+
+File Locking is a brand new feature that lets teams communicate when they are
+working on files that are difficult to merge. Users are not able to edit or push
+changes to any files that are locked by other users. While the feature has been
+in discussion for a year, we are releasing a basic Locking implementation to
+solicit feedback from the community.
+
+### Transfer Queue
+
+LFS 2.0 introduces a new Git Scanner, which walks a range of Git commits looking
+for LFS objects to transfer. The Git Scanner is now asynchronous, initiating
+large uploads or downloads in the Transfer Queue immediately once an LFS object
+is found. Previously, the Transfer Queue waited until all of the Git commits
+have been scanned before initiating the transfer. The Transfer Queue also
+automatically retries failed uploads and downloads more often.
+
+### Deprecations
+
+Git LFS v2.0.0 also drops support for the legacy API in v0.5.0. If you're still
+using LFS servers on the old API, you'll have to stick to v1.5.6.
+
+### Features
+
+* Mid-stage locking support #1769 (@sinbad)
+* Define lockable files, make read-only in working copy #1870 (@sinbad)
+* Check that files are not uncommitted before unlock #1896 (@sinbad)
+* Fix `lfs unlock --force` on a missing file #1927 (@technoweenie)
+* locking: teach pre-push hook to check for locks #1815 (@ttaylorr)
+* locking: add `--json` flag #1814 (@ttaylorr)
+* Implement local lock cache, support querying it #1760 (@sinbad)
+* support for client certificates pt 2 #1893 (@technoweenie)
+* Fix clash between progress meter and credential helper #1886 (@technoweenie)
+* Teach uninstall cmd about --local and --system #1887 (@technoweenie)
+* Add `--skip-repo` option to `git lfs install` & use in tests #1868 (@sinbad)
+* commands: convert push, pre-push to use async gitscanner #1812 (@ttaylorr)
+* tq: prioritize transferring retries before new items #1758 (@ttaylorr)
+
+### Bugs
+
+* ensure you're in the correct directory when installing #1793 (@technoweenie)
+* locking: make API requests relative to repository, not root #1818 (@ttaylorr)
+* Teach 'track' about CRLF #1914 (@technoweenie)
+* Teach 'track' how to handle empty lines in .gitattributes #1921 (@technoweenie)
+* Closing stdout pipe before function return #1861 (@monitorjbl)
+* Custom transfer terminate #1847 (@sinbad)
+* Fix Install in root problems #1727 (@technoweenie)
+* cat-file batch: read all of the bytes #1680 (@technoweenie)
+* Fixed file paths on cygwin. #1820, #1965 (@creste, @ttaylorr)
+* tq: decrement uploaded bytes in basic_upload before retry #1958 (@ttaylorr)
+* progress: fix never reading bytes with sufficiently small files #1955 (@ttaylorr)
+* tools: fix truncating string fields between balanced quotes in GIT_SSH_COMMAND #1962 (@ttaylorr)
+* commands/smudge: treat empty pointers as empty files #1954 (@ttaylorr)
+
+### Misc
+
+* all: build using Go 1.8 #1952 (@ttaylorr)
+* Embed the version information into the Windows executable #1689 (@sschuberth)
+* Add more meta-data to the Windows installer executable #1752 (@sschuberth)
+* docs/api: object size must be positive #1779 (@ttaylorr)
+* build: omit DWARF tables by default #1937 (@ttaylorr)
+* Add test to prove set operator [] works in filter matching #1768 (@sinbad)
+* test: add ntlm integration test #1840 (@technoweenie)
+* lfs/tq: completely remove legacy support #1686 (@ttaylorr)
+* remove deprecated features #1679 (@technoweenie)
+* remove legacy api support #1629 (@technoweenie)
+
+## 1.5.6 (16 February, 2017)
+
+## Bugs
+
+* Spool malformed pointers to avoid deadlock #1932 (@ttaylorr)
+
+## 1.5.5 (12 January, 2017)
+
+### Bugs
+
+* lfs: only buffer first 1k when creating a CleanPointerError #1856 (@ttaylorr)
+
+## 1.5.4 (27 December, 2016)
+
+### Bugs
+
+* progress: guard negative padding width, panic in `strings.Repeat` #1807 (@ttaylorr)
+* commands,lfs: handle malformed pointers #1805 (@ttaylorr)
+
+### Misc
+
+* script/packagecloud: release LFS on fedora/25 #1798 (@ttaylorr)
+* backport filepathfilter to v1.5.x #1782 (@technoweenie)
+
+## 1.5.3 (5 December, 2016)
+
+### Bugs
+
+* Support LFS installations at filesystem root #1732 (@technoweenie)
+* git: parse filter process header values containing '=' properly #1733 (@larsxschneider)
+* Fix SSH endpoint parsing #1738 (@technoweenie)
+
+### Misc
+
+* build: release on Go 1.7.4 #1741 (@ttaylorr)
+
+## 1.5.2 (22 November, 2016)
+
+### Features
+
+* Release LFS on Fedora 24 #1685 (@technoweenie)
+
+### Bugs
+
+* filter-process: fix reading 1024 byte files #1708 (@ttaylorr)
+* Support long paths on Windows #1705 (@technoweenie)
+
+### Misc
+
+* filter-process: exit with error if we detect an unknown command from Git #1707 (@ttaylorr)
+* vendor: remove contentaddressable lib #1706 (@technoweenie)
+
+## 1.5.1 (18 November, 2016)
+
+### Bugs
+
+* cat-file --batch parser errors on non-lfs git blobs #1680 (@technoweenie)
+
+## 1.5.0 (17 November, 2016)
+
+### Features
+
+* Filter Protocol Support #1617 (@ttaylorr, @larsxschneider)
+* Fast directory walk #1616 (@sinbad)
+* Allow usage of proxies even when contacting localhost #1605 (@chalstrick)
+
+### Bugs
+
+* start reading off the Watch() channel before sending any input #1671 (@technoweenie)
+* wait for remote ref commands to exit before returning #1656 (@jjgod, @technoweenie)
+
+### Misc
+
+* rewrite new catfilebatch implementation for upcoming gitscanner pkg #1650 (@technoweenie)
+* refactor testutils.FileInput so it's a little more clear #1666 (@technoweenie)
+* Update the lfs track docs #1642 (@technoweenie)
+* Pre push tracing #1638 (@technoweenie)
+* Remove `AllGitConfig()` #1634 (@technoweenie)
+* README: set minimal required Git version to 1.8.5 #1636 (@larsxschneider)
+* 'smudge --info' is deprecated in favor of 'ls-files' #1631 (@technoweenie)
+* travis-ci: test GitLFS with ancient Git version #1626 (@larsxschneider)
+
+## 1.4.4 (24 October, 2016)
+
+### Bugs
+
+* transfer: more descriptive "expired at" errors #1603 (@ttaylorr)
+* commands,lfs/tq: Only send unique OIDs to the Transfer Queue #1600 (@ttaylorr)
+* Expose the result message in case of an SSH authentication error #1599 (@sschuberth)
+
+### Misc
+
+* AppVeyor: Do not build branches with open pull requests #1594 (@sschuberth)
+* Update .mailmap #1593 (@dpursehouse)
+
+## 1.4.3 (17 October, 2016)
+
+### Bugs
+
+* lfs/tq: use extra arguments given to tracerx.Printf #1583 (@ttaylorr)
+* api: correctly print legacy API warning to Stderr #1582 (@ttaylorr)
+
+### Misc
+
+* Test storage retries #1585 (@ttaylorr)
+* Test legacy check retries behavior #1584 (@ttaylorr)
+* docs: Fix a link to the legacy API #1579 (@sschuberth)
+* Add a .mailmap file #1577 (@sschuberth)
+* Add a large wizard image to the Windows installer #1575 (@sschuberth)
+* Appveyor badge #1574 (@ttaylorr)
+
+## 1.4.2 (10 October, 2016)
+
+v1.4.2 brings a number of bug fixes and usability improvements to LFS. This
+release also adds support for multiple retries within the transfer queue, making
+transfers much more reliable. To enable this feature, see the documentation for
+`lfs.transfer.maxretries` in `git-lfs-config(5)`.
+
+We'd also like to extend a special thank-you to @sschuberth who undertook the
+process of making LFS's test run on Windows through AppVeyor. Now all pull
+requests run tests on macOS, Linux, and Windows.
+
+### Features
+
+* lfs: warn on usage of the legacy API #1564 (@ttaylorr)
+* use filepath.Clean() when comparing filenames to include/exclude patterns #1565 (@technoweenie)
+* lfs/transfer_queue: support multiple retries per object #1505, #1528, #1535, #1545 (@ttaylorr)
+* Automatically upgrade old filters instead of requiring ��force #1497 (@sinbad)
+* Allow lfs.pushurl in .lfsconfig #1489 (@technoweenie)
+
+### Bugs
+
+* Use "sha256sum" on Windows  #1566 (@sschuberth)
+* git: ignore non-root wildcards #1563 (@ttaylorr)
+* Teach status to recognize multiple files with identical contents #1550 (@ttaylorr)
+* Status initial commit #1540 (@sinbad)
+* Make path comparison robust against Windows short / long path issues #1523 (@sschuberth)
+* Allow fetch to run without a remote configured #1507 (@sschuberth)
+
+### Misc
+
+* travis: run tests on Go 1.7.1 #1568 (@ttaylorr)
+* Enable running tests on AppVeyor CI #1567 (@sschuberth)
+* Travis: Only install git if not installed yet #1557 (@sschuberth)
+* Windows test framework fixes #1522 (@sschuberth)
+* Simplify getting the absolute Git root directory #1518 (@sschuberth)
+* Add icons to the Windows installer #1504 (@sschuberth)
+* docs/man: reference git-lfs-pointer(1) in clean documentation #1503 (@ttaylorr)
+* Make AppVeyor CI for Windows work again #1506 (@sschuberth)
+* commands: try out RegisterCommand() #1495 (@technoweenie)
+
+## 1.4.1 (26 August, 2016)
+
+### Features
+
+* retry if file download failed #1454 (@larsxschneider)
+* Support wrapped clone in current directory #1478 (@ttaylorr)
+
+### Misc
+
+* Test `RetriableReader` #1482 (@ttaylorr)
+
+## 1.4.0 (19 August, 2016)
+
+### Features
+
+* Install LFS at the system level when packaged #1460 (@javabrett)
+* Fetch remote urls #1451 (@technoweenie)
+* add object Authenticated property #1452 (@technoweenie)
+* add support for `url.*.insteadof` in git config #1117, #1443 (@artagnon, @technoweenie)
+
+### Bugs
+
+* fix --include bug when multiple files have same lfs content #1458 (@technoweenie)
+* check the git version is ok in some key commands #1461 (@technoweenie)
+* fix duplicate error reporting #1445, #1453 (@dpursehouse, @technoweenie)
+* transfer/custom: encode "event" as lowercase #1441 (@ttaylorr)
+
+### Misc
+
+* docs/man: note GIT_LFS_PROGRESS #1469 (@ttaylorr)
+* Reword the description of HTTP 509 status #1467 (@dpursehouse)
+* Update fetch include/exclude docs for pattern matching #1455 (@ralfthewise)
+* config-next: API changes to the `config` package #1425 (@ttaylorr)
+* errors-next: Contextualize error messages #1463 (@ttaylorr, @technoweenie)
+* scope commands to not leak instances of themselves #1434 (@technoweenie)
+* Transfer manifest #1430 (@technoweenie)
+
+## 1.3.1 (2 August 2016)
+
+### Features
+
+* lfs/hook: teach `lfs.Hook` about `core.hooksPath` #1409 (@ttaylorr)
+
+### Bugs
+
+* distinguish between empty include/exclude paths #1411 (@technoweenie)
+* Fix sslCAInfo config lookup when host in config doesn't have a trailing slash #1404 (@dakotahawkins)
+
+### Misc
+
+* Use commands.Config instead of config.Config #1390 (@technoweenie)
+
+## 1.3.0 (21 July 2016)
+
+### Features
+
+* use proxy from git config #1173, #1358 (@jonmagic, @LizzHale, @technoweenie)
+* Enhanced upload/download of LFS content: #1265 #1279 #1297 #1303 #1367 (@sinbad)
+  * Resumable downloads using HTTP range headers
+  * Resumable uploads using [tus.io protocol](http://tus.io)
+  * Pluggable [custom transfer adapters](https://github.com/git-lfs/git-lfs/blob/master/docs/custom-transfers.md)
+* In git 2.9+, run "git lfs pull" in submodules after "git lfs clone" #1373 (@sinbad)
+* cmd,doc,test: teach `git lfs track --{no-touch,verbose,dry-run}` #1344 (@ttaylorr)
+* ⏳ Retry transfers with expired actions #1350 (@ttaylorr)
+* Safe track patterns #1346 (@ttaylorr)
+* Add checkout --unstaged flag #1262 (@orivej)
+* cmd/clone: add include/exclude via flags and config #1321 (@ttaylorr)
+* Improve progress reporting when files skipped #1296 (@sinbad)
+* Experimental file locking commands #1236, #1259, #1256, #1386 (@ttaylorr)
+* Implement support for GIT_SSH_COMMAND #1260 (@pdf)
+* Recognize include/exclude filters from config #1257 (@ttaylorr)
+
+### Bugs
+
+* Fix bug in Windows installer under Win32. #1200 (@teo-tsirpanis)
+* Updated request.GetAuthType to handle multi-value auth headers #1379 (@VladimirKhvostov)
+* Windows fixes #1374 (@sinbad)
+* Handle artifactory responses #1371 (@ttaylorr)
+* use `git rev-list --stdin` instead of passing each remote ref #1359 (@technoweenie)
+* docs/man: move "logs" subcommands from OPTIONS to COMMANDS #1335 (@ttaylorr)
+* test/zero-len: update test for git v2.9.1 #1369 (@ttaylorr)
+* Unbreak building httputil on OpenBSD #1360 (@jasperla)
+* WIP transferqueue race fix #1255 (@technoweenie)
+* Safety check to `comands.requireStdin` #1349 (@ttaylorr)
+* Removed CentOS 5 from dockers. Fixed #1295. #1298 (@javabrett)
+* Fix 'git lfs fetch' with a sha1 ref #1323 (@omonnier)
+* Ignore HEAD ref when fetching with --all #1310 (@ttaylorr)
+* Return a fully remote ref to reduce chances of ref clashes #1248 (@technoweenie)
+* Fix reporting of `git update-index` errors in `git lfs checkout` and `git lfs pull` #1400 (@technoweenie)
+
+### Misc
+
+* Added Linux Mint Sarah to package cloud script #1384 (@andyneff)
+* travis-ci: require successful tests against upcoming Git core release #1372 (@larsxschneider)
+* travis-ci: add a build job to test against upcoming versions of Git #1361 (@larsxschneider)
+* Create Makefiles for building with gccgo #1222 (@zeldin)
+* README: add @ttaylorr to core team #1332 (@ttaylorr)
+* Enforced a minimum gem version of 1.0.4 for packagecloud-ruby #1292 (@javabrett)
+* I think this should be "Once installed" and not "One installed", but … #1305 (@GabLeRoux)
+* script/test: propagate extra args to go test #1324 (@omonnier)
+* Add `lfs.basictransfersonly` option to disable non-basic transfer adapters #1299 (@sinbad)
+* Debian build vendor test excludes #1291 (@javabrett)
+* gitignore: ignore lfstest-\* files #1271 (@ttaylorr)
+* Disable gojsonschema test, causes failures when firewalls block it #1274 (@sinbad)
+* test: use noop credential helper for auth tests #1267 (@ttaylorr)
+* get git tests passing when run outside of repository #1229 (@technoweenie)
+* Package refactor no.1 #1226 (@sinbad)
+* vendor: vendor dependencies in vendor/ using Glide #1243 (@ttaylorr)
+
+## 1.2.1 (2 June 2016)
+
+### Features
+
+* Add missing config details to `env` command #1217 (@sinbad)
+* Allow smudge filter to return 0 on download failure #1213 (@sinbad)
+* Add `git lfs update --manual` option & promote it on hook install fail #1182 (@sinbad)
+* Pass `git lfs clone` flags through to `git clone` correctly, respect some options #1160 (@sinbad)
+
+### Bugs
+
+* Clean trailing `/` from include/exclude paths #1278 (@ttaylorr)
+* Fix problems with user prompts in `git lfs clone` #1185 (@sinbad)
+* Fix failure to return non-zero exit code when lfs install/update fails to install hooks #1178 (@sinbad)
+* Fix missing man page #1149 (@javabrett)
+* fix concurrent map read and map write #1179 (@technoweenie)
+
+### Misc
+
+* Allow additional fields on request & response schema #1276 (@sinbad)
+* Fix installer error on win32. #1198 (@teo-tsirpanis)
+* Applied same -ldflags -X name value -> name=value fix #1193 (@javabrett)
+* add instructions to install from MacPorts #1186 (@skymoo)
+* Add xenial repo #1170 (@graingert)
+
+## 1.2.0 (14 April 2016)
+
+### Features
+
+* netrc support #715 (@rubyist)
+* `git lfs clone` command #988 (@sinbad)
+* Support self-signed certs #1067 (@sinbad)
+* Support sslverify option for specific hosts #1081 (@sinbad)
+* Stop transferring duplicate objects on major push or fetch operations on multiple refs. #1128 (@technoweenie)
+* Touch existing git tracked files when tracked in LFS so they are flagged as modified #1104 (@sinbad)
+* Support for git reference clones #1007 (@jlehtnie)
+
+### Bugs
+
+* Fix clean/smudge filter string for files starting with - #1083 (@epriestley)
+* Fix silent failure to push LFS objects when ref matches a filename in the working copy #1096 (@epriestley)
+* Fix problems with using LFS in symlinked folders #818 (@sinbad)
+* Fix git lfs push silently misbehaving on ambiguous refs; fail like git push instead #1118 (@sinbad)
+* Whitelist `lfs.*.access` config in local ~/.lfsconfig #1122 (@rjbell4)
+* Only write the encoded pointer information to Stdout #1105 (@sschuberth)
+* Use hardcoded auth from remote or lfs config when accessing the storage api #1136 (@technoweenie, @jonmagic)
+* SSH should be called more strictly with command as one argument #1134 (@sinbad)
+
+## 1.1.2 (1 March, 2016)
+
+* Fix Base64 issues with `?` #989 (@technoweenie)
+* Fix zombie git proc issue #1012 (@rlaakkol)
+* Fix problems with files containing unicode characters #1016 (@technoweenie)
+* Fix panic in `git cat-file` parser #1006 (@technoweenie)
+* Display error messages in non-fatal errors #1028 #1039 #1042 (@technoweenie)
+* Fix concurrent map access in progress meter (@technoweenie)
+
+## 1.1.1 (4 February, 2016)
+
+### Features
+
+* Add copy-on-write support for Linux BTRFS filesystem #952 (@bozaro)
+* convert `git://` remotes to LFS servers automatically #964 (@technoweenie)
+* Fix `git lfs track` handling of absolute paths. #975  (@technoweenie)
+* Allow tunable http client timeouts #977 (@technoweenie)
+
+### Bugs
+
+* Suppress git config warnings for non-LFS keys #861 (@technoweenie)
+* Fix fallthrough when `git-lfs-authenticate` returns an error #909 (@sinbad)
+* Fix progress bar issue #883 (@pokehanai)
+* Support `remote.name.pushurl` config #949 (@sinbad)
+* Fix handling of `GIT_DIR` and `GIT_WORK_TREE` #963, #971 (@technoweenie)
+* Fix handling of zero length files #966 (@nathanhi)
+* Guard against invalid remotes passed to `push` and `pre-push` #974 (@technoweenie)
+* Fix race condition in `git lfs pull` #972 (@technoweenie)
+
+### Extra
+
+* Add server API test tool #868 (@sinbad)
+* Redo windows installer with innosetup #875 (@strich)
+* Pre-built packages are built with Go v1.5.3
+
+## 1.1.0 (18 November, 2015)
+
+* NTLM auth support #820 (@WillHipschman, @technoweenie)
+* Add `prune` command #742 (@sinbad)
+* Use .lfsconfig instead of .gitconfig #837 (@technoweenie)
+* Rename "init" command #838 (@technoweenie)
+* Raise error if credentials are needed #842 (@technoweenie)
+* Support git repos in symlinked directories #818 (@sinbad, @difro, @jiangxin)
+* Fix "git lfs env" to show correct SSH remote info #828 (@jiangxin)
+
+## 1.0.2 (28 October, 2015)
+
+* Fix issue with 'git lfs smudge' and the batch API. #795 (@technoweenie)
+* Fix race condition in the git scanning code. #801 (@technoweenie)
+
+## 1.0.1 (23 October, 2015)
+
+* Downcase git config keys (prevents Auth loop) #690 (@WillHipschman)
+* Show more info for unexpected http responses #710 (@rubyist)
+* Use separate stdout/stderr buffers for `git-lfs-authenticate` #718 (@bozaro)
+* Use LoggedError instead of Panic if update-index fails in checkout #735 (@sinbad)
+* `smudge` command exits with non-zero if the download fails #732 (@rubyist)
+* Use `git rev-parse` to find the git working dir #692 (@sinbad)
+* Improved default remote behaviour & validation for fetch/pull #713 (@sinbad)
+* Make fetch return error code when 1+ downloads failed #734 (@sinbad)
+* Improve lfs.InRepo() detection in `init`/`update` #756 (@technoweenie)
+* Teach smudge to use the batch api #711 (@rubyist)
+* Fix not setting global attribute when needed to b/c of local state #765 (@sinbad)
+* Fix clone fail when fetch is excluded globally #770 (@sinbad)
+* Fix for partial downloads problem #763 (@technoweenie)
+* Get integration tests passing on Windows #771 (@sinbad)
+
+### Security
+
+* Whitelist the valid keys read from .gitconfig #760 (@technoweenie)
+
+This prevents unsafe git configuration values from being used by Git LFS.
+
+## v1.0 (1 October, 2015)
+
+* Manual reference is integrated into the "help" options #665 @sinbad
+* Fix `ls-files` when run from an empty repository #668 @Aorjoa
+* Support listing duplicate files in `ls-files` #681 @Aorjoa @technoweenie
+* `update` and `init` commands can install the pre-push hook in bare repositories #671 @technoweenie
+* Add `GIT_LFS_SKIP_SMUDGE` and `init --skip-smudge` #679 @technoweenie
+
+## v0.6.0 (10 September, 2015)
+
+This is the first release that uses the new Batch API by default, while still
+falling back to the Legacy API automatically. Also, new fetch/checkout/push
+commands have been added.
+
+Run `git lfs update` in any local repositories to make sure all config settings
+are updated.
+
+### Fetch
+
+* Rename old `git lfs fetch` command to `git lfs pull`. #527 (@sinbad)
+* Add `git lfs checkout` #527 #543 #551 #566 (@sinbad)
+* Add `git lfs fetch` for _just_ downloading objects. #527 (@sinbad)
+  * Add `remote` arg, and default to tracking remote instead of "origin". #583 (@sinbad)
+  * Support fetching multiple refs #542 (@sinbad)
+  * Add `--include` and `--exclude` flag for `git lfs fetch` #573 (@sinbad)
+  * Add `--recent` flag for downloading recent files outside of the current
+    checkout. #610 (@sinbad)
+  * Add `--all` option for download all objects from the server. #633 (@sinbad)
+* Fix error handling while `git update-index` is running. #570 (@rubyist)
+
+See [git-lfs-fetch(1)](https://github.com/git-lfs/git-lfs/blob/v0.6.0/docs/man/git-lfs-fetch.1.ronn),
+[git-lfs-checkout(1)](https://github.com/git-lfs/git-lfs/blob/v0.6.0/docs/man/git-lfs-checkout.1.ronn),
+and [git-lfs-pull(1)](https://github.com/git-lfs/git-lfs/blob/v0.6.0/docs/man/git-lfs-pull.1.ronn)
+ for details.
+
+### Push
+
+* Support pushing multiple branches in the pre-push hook. #635 (@sinbad)
+* Fix pushing objects from a branch that's not HEAD. #608 (@sinbad)
+* Check server for objects before failing push because local is missing. #581 (@sinbad)
+* Filter out commits from remote refs when pushing. #578 (@billygor)
+* Support pushing all objects to the server, regardless of the remote ref. #646 (@technoweenie)
+* Fix case where pre-push git hook exits with 0. #582 (@sinbad)
+
+See [git-lfs-push(1)](https://github.com/git-lfs/git-lfs/blob/v0.6.0/docs/man/git-lfs-push.1.ronn) for details.
+
+### API Clients
+
+* Fix some race conditions in the Batch API client. #577 #637 (@sinbad, @rubyist)
+* Support retries in the Batch API client. #595 (@rubyist)
+* Fix hanging batch client in certain error conditions. #594 (@rubyist)
+* Treat 401 responses as errors in the Legacy API client. #634 (@rubyist)
+* Fix bug in the Legacy API client when the object already exists on the server. #572 (@billygor)
+
+### Credentials
+
+* Fix how git credentials are checked in certain edge cases. #611 #650 #652 (@technoweenie)
+* Send URI user to git credentials. #626 (@sinbad)
+* Support git credentials with useHttpPath enabled. #554 (@clareliguori)
+
+### Installation
+
+* Docker images and scripts for building and testing linux packages. #511 #526 #555 #603 (@andyneff, @ssgelm)
+* Create Windows GUI installer. #642 (@technoweenie)
+* Binary releases use Go 1.5, which includes fix for Authorization when the
+  request URL includes just the username. [golang/go#11399](https://github.com/golang/go/issues/11399)
+
+### Misc
+
+* Documented Git config values used by Git LFS in [git-lfs-config(5)](https://github.com/git-lfs/git-lfs/blob/v0.6.0/docs/man/git-lfs-config.5.ronn). #610 (@sinbad)
+* Experimental support for Git worktrees (in Git 2.5+) #546 (@sinbad)
+* Experimental extension support. #486 (@ryansimmen)
+
+## v0.5.4 (30 July, 2015)
+
+* Ensure `git lfs uninit` cleans your git config thoroughly. #530 (@technoweenie)
+* Fix issue with asking `git-credentials` for auth details after getting them
+from the SSH command. #534 (@technoweenie)
+
+## v0.5.3 (23 July, 2015)
+
+* `git lfs fetch` bugs #429 (@rubyist)
+* Push can crash on 32 bit architectures #450 (@rubyist)
+* Improved SSH support #404, #464 (@sinbad, @technoweenie)
+* Support 307 redirects with relative url #442 (@sinbad)
+* Fix `init` issues when upgrading #446 #451 #452 #465 (@technoweenie, @rubyist)
+* Support chunked Transfer-Encoding #386 (@ryansimmen)
+* Fix issue with pushing deleted objects #461 (@technoweenie)
+* Teach `git lfs push` how to send specific objects #449 (@larsxschneider)
+* Update error message when attempting to push objects that don't exist in `.git/lfs/objects` #447 (@technoweenie)
+* Fix bug in HTTP client when response body is nil #472 #488 (@rubyist, @technoweenie)
+* `-crlf` flag in gitattributes is deprecated #475 (@technoweenie)
+* Improvements to the CentOS and Debian build and package scripts (@andyneff, @ssgelm)
+
+## v0.5.2 (19 June, 2015)
+
+* Add `git lfs fetch` command for downloading objects. #285 (@rubyist)
+* Fix `git lfs track` issues when run outside of a git repository #312, #323 (@michael-k, @Aorjoa)
+* Fix `git lfs track` for paths with spaces in them #327 (@technoweenie)
+* Fix `git lfs track` by writing relative paths to .gitattributes #356 (@michael-k)
+* Fix `git lfs untrack` so it doesn't remove entries incorrectly from .gitattributes #398 (@michael-k)
+* Fix `git lfs clean` bug with zero length files #346 (@technoweenie)
+* Add `git lfs fsck` #373 (@zeroshirts, @michael-k)
+* The Git pre-push warns if Git LFS is not installed #339 (@rubyist)
+* Fix Content-Type header sent by the HTTP client #329 (@joerg)
+* Improve performance tracing while scanning refs #311 (@michael-k)
+* Fix detection of LocalGitDir and LocalWorkingDir #312 #354 #361 (@michael-k)
+* Fix inconsistent file mode bits for directories created by Git LFS #364 (@michael-k)
+* Optimize shell execs #377, #382, #391 (@bozaro)
+* Collect HTTP transfer stats #366, #400 (@rubyist)
+* Support GIT_DIR and GIT_WORK_TREE #370 (@michael-k)
+* Hide Git application window in Windows #381 (@bozaro)
+* Add support for configured URLs containing credentials per RFC1738 #408 (@ewbankkit, @technoweenie)
+* Add experimental support for batch API calls #285 (@rubyist)
+* Improve linux build instructions for CentOS and Debian. #299 #309 #313 #332 (@jsh, @ssgelm, @andyneff)
+
+## v0.5.1 (30 April, 2015)
+
+* Fix Windows install.bat script.  #223 (@PeterDaveHello)
+* Fix bug where `git lfs clean` will clean Git LFS pointers too #271 (@technoweenie)
+* Better timeouts for the HTTP client #215 (@Mistobaan)
+* Concurrent uploads through `git lfs push` #258 (@rubyist)
+* Fix `git lfs smudge` behavior with zero-length file in `.git/lfs/objects` #267 (@technoweenie)
+* Separate out pre-push hook behavior from `git lfs push` #263 (@technoweenie)
+* Add diff/merge properties to .gitattributes #265 (@technoweenie)
+* Respect `GIT_TERMINAL_PROMPT ` #257 (@technoweenie)
+* Fix CLI progress bar output #185 (@technoweenie)
+* Fail fast in `clean` and `smudge` commands when run without STDIN #264 (@technoweenie)
+* Fix shell quoting in pre-push hook.  #235 (@mhagger)
+* Fix progress bar output during file uploads.  #185 (@technoweenie)
+* Change `remote.{name}.lfs_url` to `remote.{name}.lfsurl` #237 (@technoweenie)
+* Swap `git config` order.  #245 (@technoweenie)
+* New `git lfs pointer` command for generating and comparing pointers #246 (@technoweenie)
+* Follow optional "href" property from git-lfs-authenticate SSH command #247 (@technoweenie)
+* `.git/lfs/objects` spec clarifications: #212 (@rtyley), #244 (@technoweenie)
+* man page updates: #228 (@mhagger)
+* pointer spec clarifications: #246 (@technoweenie)
+* Code comments for the untrack command: #225 (@thekafkaf)
+
+## v0.5.0 (10 April, 2015)
+
+* Initial public release

README.md

@@ -1,19 +1,248 @@
----
-language: "en"
-thumbnail: "Keywords to Sentences"
-tags:
-- keytotext
-- k2t
-- Keywords to Sentences
-
-model-index:
-- name: t5-small
----
-
-Idea is to build a model which will take keywords as inputs and generate sentences as outputs.
-
-Potential use case can include: 
-- Marketing 
-- Search Engine Optimization
-- Topic generation etc.
-- Fine tuning of topic modeling models
+# Git Large File Storage
+
+[![CI status][ci_badge]][ci_url]
+
+[ci_badge]: https://github.com/git-lfs/git-lfs/workflows/CI/badge.svg
+[ci_url]: https://github.com/git-lfs/git-lfs/actions?query=workflow%3ACI
+
+[Git LFS](https://git-lfs.github.com) is a command line extension and
+[specification](docs/spec.md) for managing large files with Git.
+
+The client is written in Go, with pre-compiled binaries available for Mac,
+Windows, Linux, and FreeBSD. Check out the [website](http://git-lfs.github.com)
+for an overview of features.
+
+## Getting Started
+
+### Downloading
+
+You can install the Git LFS client in several different ways, depending on your
+setup and preferences.
+
+* **Linux users**. Debian and RPM packages are available from
+  [PackageCloud](https://packagecloud.io/github/git-lfs/install).
+* **macOS users**. [Homebrew](https://brew.sh) bottles are distributed, and can
+  be installed via `brew install git-lfs`.
+* **Windows users**. Git LFS is included in the distribution of
+  [Git for Windows](https://gitforwindows.org/). Alternatively, you can
+  install a recent version of Git LFS from the [Chocolatey](https://chocolatey.org/) package manager.
+* **Binary packages**. In addition, [binary packages](https://github.com/git-lfs/git-lfs/releases) are
+available for Linux, macOS, Windows, and FreeBSD.
+* **Building from source**. [This repository](https://github.com/git-lfs/git-lfs.git) can also be
+built from source using the latest version of [Go](https://golang.org), and the
+available instructions in our
+[Wiki](https://github.com/git-lfs/git-lfs/wiki/Installation#source).
+
+### Installing
+
+#### From binary
+
+The [binary packages](https://github.com/git-lfs/git-lfs/releases) include a script which will:
+
+- Install Git LFS binaries onto the system `$PATH`
+- Run `git lfs install` to
+perform required global configuration changes.
+
+```ShellSession
+$ ./install.sh
+```
+
+#### From source
+
+- Ensure you have the latest version of Go, GNU make, and a standard Unix-compatible build environment installed.
+- On Windows, install `goversioninfo` with `go get github.com/josephspurrier/goversioninfo/cmd/goversioninfo`.
+- Run `make`.
+- Place the `git-lfs` binary, which can be found in `bin`, on your system’s executable `$PATH` or equivalent.
+- Git LFS requires global configuration changes once per-machine. This can be done by
+running:
+
+```ShellSession
+$ git lfs install
+```
+
+#### Verifying releases
+
+Releases are signed with the OpenPGP key of one of the core team members.  To
+get these keys, you can run the following command, which will print them to
+standard output:
+
+```ShellSession
+$ curl -L https://api.github.com/repos/git-lfs/git-lfs/tarball/core-gpg-keys | tar -Ozxf -
+```
+
+Once you have the keys, you can download the `sha256sums.asc` file and verify
+the file you want like so:
+
+```ShellSession
+$ gpg -d sha256sums.asc | grep git-lfs-linux-amd64-v2.10.0.tar.gz | shasum -a 256 -c
+```
+
+## Example Usage
+
+To begin using Git LFS within a Git repository that is not already configured
+for Git LFS, you can indicate which files you would like Git LFS to manage.
+This can be done by running the following _from within a Git repository_:
+
+```bash
+$ git lfs track "*.psd"
+```
+
+(Where `*.psd` is the pattern of filenames that you wish to track. You can read
+more about this pattern syntax
+[here](https://git-scm.com/docs/gitattributes)).
+
+> *Note:* the quotation marks surrounding the pattern are important to
+> prevent the glob pattern from being expanded by the shell.
+
+After any invocation of `git-lfs-track(1)` or `git-lfs-untrack(1)`, you _must
+commit changes to your `.gitattributes` file_. This can be done by running:
+
+```bash
+$ git add .gitattributes
+$ git commit -m "track *.psd files using Git LFS"
+```
+
+You can now interact with your Git repository as usual, and Git LFS will take
+care of managing your large files. For example, changing a file named `my.psd`
+(tracked above via `*.psd`):
+
+```bash
+$ git add my.psd
+$ git commit -m "add psd"
+```
+
+> _Tip:_ if you have large files already in your repository's history, `git lfs
+> track` will _not_ track them retroactively. To migrate existing large files
+> in your history to use Git LFS, use `git lfs migrate`. For example:
+>
+> ```
+> $ git lfs migrate import --include="*.psd" --everything
+> ```
+>
+> For more information, read [`git-lfs-migrate(1)`](https://github.com/git-lfs/git-lfs/blob/main/docs/man/git-lfs-migrate.1.ronn).
+
+You can confirm that Git LFS is managing your PSD file:
+
+```bash
+$ git lfs ls-files
+3c2f7aedfb * my.psd
+```
+
+Once you've made your commits, push your files to the Git remote:
+
+```bash
+$ git push origin main
+Uploading LFS objects: 100% (1/1), 810 B, 1.2 KB/s
+# ...
+To https://github.com/git-lfs/git-lfs-test
+   67fcf6a..47b2002  main -> main
+```
+
+Note: Git LFS requires at least Git 1.8.2 on Linux or 1.8.5 on macOS.
+
+### Uninstalling
+
+If you've decided that Git LFS isn't right for you, you can convert your
+repository back to a plain Git repository with `git lfs migrate` as well.  For
+example:
+
+```ShellSession
+$ git lfs migrate export --include="*.psd" --everything
+```
+
+Note that this will rewrite history and change all of the Git object IDs in your
+repository, just like the import version of this command.
+
+If there's some reason that things aren't working out for you, please let us
+know in an issue, and we'll definitely try to help or get it fixed.
+
+## Limitations
+
+Git LFS maintains a list of currently known limitations, which you can find and
+edit [here](https://github.com/git-lfs/git-lfs/wiki/Limitations).
+
+Git LFS source code utilizes Go modules in its build system, and therefore this
+project contains a `go.mod` file with a defined Go module path.  However, we
+do not maintain a stable Go language API or ABI, as Git LFS is intended to be
+used solely as a compiled binary utility.  Please do not import the `git-lfs`
+module into other Go code and do not rely on it as a source code dependency.
+
+## Need Help?
+
+You can get help on specific commands directly:
+
+```bash
+$ git lfs help <subcommand>
+```
+
+The [official documentation](docs) has command references and specifications for
+the tool.  There's also a [FAQ](https://github.com/git-lfs/git-lfs/wiki/FAQ) on
+the wiki which answers some common questions.
+
+If you have a question on how to use Git LFS, aren't sure about something, or
+are looking for input from others on tips about best practices or use cases,
+feel free to
+[start a discussion](https://github.com/git-lfs/git-lfs/discussions).
+
+You can always [open an issue](https://github.com/git-lfs/git-lfs/issues), and
+one of the Core Team members will respond to you. Please be sure to include:
+
+1. The output of `git lfs env`, which displays helpful information about your
+   Git repository useful in debugging.
+2. Any failed commands re-run with `GIT_TRACE=1` in the environment, which
+   displays additional information pertaining to why a command crashed.
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for info on working on Git LFS and
+sending patches. Related projects are listed on the [Implementations wiki
+page](https://github.com/git-lfs/git-lfs/wiki/Implementations).
+
+See also [SECURITY.md](SECURITY.md) for info on how to submit reports
+of security vulnerabilities.
+
+## Core Team
+
+These are the humans that form the Git LFS core team, which runs the project.
+
+In alphabetical order:
+
+| [@bk2204][bk2204-user] | [@chrisd8088][chrisd8088-user] | [@larsxschneider][larsxschneider-user] |
+| :---: | :---: | :---: |
+| [![][bk2204-img]][bk2204-user] | [![][chrisd8088-img]][chrisd8088-user] | [![][larsxschneider-img]][larsxschneider-user] |
+| [PGP 0223B187][bk2204-pgp] | [PGP 088335A9][chrisd8088-pgp] | [PGP A5795889][larsxschneider-pgp] |
+
+[bk2204-img]: https://avatars1.githubusercontent.com/u/497054?s=100&v=4
+[chrisd8088-img]: https://avatars1.githubusercontent.com/u/28857117?s=100&v=4
+[larsxschneider-img]: https://avatars1.githubusercontent.com/u/477434?s=100&v=4
+[bk2204-user]: https://github.com/bk2204
+[chrisd8088-user]: https://github.com/chrisd8088
+[larsxschneider-user]: https://github.com/larsxschneider
+[bk2204-pgp]: https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x88ace9b29196305ba9947552f1ba225c0223b187
+[chrisd8088-pgp]: https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x86cd3297749375bcf8206715f54fe648088335a9
+[larsxschneider-pgp]: https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xaa3b3450295830d2de6db90caba67be5a5795889
+
+### Alumni
+
+These are the humans that have in the past formed the Git LFS core team, or
+have otherwise contributed a significant amount to the project. Git LFS would
+not be possible without them.
+
+In alphabetical order:
+
+| [@andyneff][andyneff-user] | [@PastelMobileSuit][PastelMobileSuit-user] | [@rubyist][rubyist-user] | [@sinbad][sinbad-user] | [@technoweenie][technoweenie-user] | [@ttaylorr][ttaylorr-user] |
+| :---: | :---: | :---: | :---: | :---: | :---: |
+| [![][andyneff-img]][andyneff-user] | [![][PastelMobileSuit-img]][PastelMobileSuit-user] | [![][rubyist-img]][rubyist-user] | [![][sinbad-img]][sinbad-user] | [![][technoweenie-img]][technoweenie-user] | [![][ttaylorr-img]][ttaylorr-user] |
+
+[andyneff-img]: https://avatars1.githubusercontent.com/u/7596961?v=3&s=100
+[PastelMobileSuit-img]: https://avatars2.githubusercontent.com/u/37254014?s=100&v=4
+[rubyist-img]: https://avatars1.githubusercontent.com/u/143?v=3&s=100
+[sinbad-img]: https://avatars1.githubusercontent.com/u/142735?v=3&s=100
+[technoweenie-img]: https://avatars3.githubusercontent.com/u/21?v=3&s=100
+[ttaylorr-img]: https://avatars2.githubusercontent.com/u/443245?s=100&v=4
+[andyneff-user]: https://github.com/andyneff
+[PastelMobileSuit-user]: https://github.com/PastelMobileSuit
+[sinbad-user]: https://github.com/sinbad
+[rubyist-user]: https://github.com/rubyist
+[technoweenie-user]: https://github.com/technoweenie
+[ttaylorr-user]: https://github.com/ttaylorr

git-lfs-linux-amd64-v3.0.2.tar.gz

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:796f5ea0259eabe57f94a8ad1bb0d46806168df30b135a65d88f8a7ee1409e0b
+size 4066152

install.sh

@@ -0,0 +1,22 @@
+#!/usr/bin/env bash
+set -eu
+
+prefix="/home/ldkhang4869/anaconda3/envs/test"
+
+if [ "${PREFIX:-}" != "" ] ; then
+  prefix=${PREFIX:-}
+elif [ "${BOXEN_HOME:-}" != "" ] ; then
+  prefix=${BOXEN_HOME:-}
+fi
+
+mkdir -p $prefix/bin
+rm -rf $prefix/bin/git-lfs*
+
+pushd "$( dirname "${BASH_SOURCE[0]}" )" > /dev/null
+  for g in git*; do
+    install $g "$prefix/bin/$g"
+  done
+popd > /dev/null
+
+PATH+=:$prefix/bin
+git lfs install

man/git-lfs-checkout.1

@@ -0,0 +1,62 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-CHECKOUT" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-checkout\fR \- Update working copy with file content if available
+.
+.SH "SYNOPSIS"
+\fBgit lfs checkout\fR \fIfilespec\fR\.\.\. \fBgit lfs checkout\fR \-\-to \fIpath\fR { \-\-ours | \-\-theirs | \-\-base } \fIfile\fR\.\.\.
+.
+.SH "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\.
+.
+.P
+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\.
+.
+.P
+Filespecs can be provided as arguments to restrict the files which are updated\.
+.
+.P
+When used with \fB\-\-to\fR and the working tree is in a conflicted state due to a merge, this option checks out one of the three stages of the conflict into a separate file\. This can make using diff tools to inspect and resolve merges easier\.
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-\-base\fR
+Check out the merge base of the specified file\.
+.
+.TP
+\fB\-\-ours\fR
+Check out our side (that of the current branch) of the conflict for the specified file\.
+.
+.TP
+\fB\-\-theirs\fR
+Check out their side (that of the other branch) of the conflict for the specified file\.
+.
+.TP
+\fB\-\-to\fR \fIpath\fR
+If the working tree is in a conflicted state, check out the portion of the conflict specified by \fB\-\-base\fR, \fB\-\-ours\fR, or \fB\-\-theirs\fR to the given path\.
+.
+.SH "EXAMPLES"
+.
+.IP "\(bu" 4
+Checkout all files that are missing or placeholders
+.
+.IP
+\fBgit lfs checkout\fR
+.
+.IP "\(bu" 4
+Checkout a specific couple of files
+.
+.IP
+\fBgit lfs checkout path/to/file1\.png path/to\.file2\.png\fR
+.
+.IP "" 0
+.
+.SH "SEE ALSO"
+git\-lfs\-fetch(1), git\-lfs\-pull(1)\.
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-checkout.1.html

@@ -0,0 +1,138 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-checkout(1) - Update working copy with file content if available</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#OPTIONS">OPTIONS</a>
+    <a href="#EXAMPLES">EXAMPLES</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-checkout(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-checkout(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-checkout</code> - <span class="man-whatis">Update working copy with file content if available</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs checkout</code> <var>filespec</var>...
+<code>git lfs checkout</code> --to <var>path</var> { --ours | --theirs | --base } <var>file</var>...</p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>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 <span class="man-ref">git-lfs-fetch<span class="s">(1)</span></span> for that.</p>
+
+<p>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.</p>
+
+<p>Filespecs can be provided as arguments to restrict the files which are updated.</p>
+
+<p>When used with <code>--to</code> and the working tree is in a conflicted state due to a
+merge, this option checks out one of the three stages of the conflict into a
+separate file. This can make using diff tools to inspect and resolve merges
+easier.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<dl>
+<dt class="flush"><code>--base</code></dt><dd><p>Check out the merge base of the specified file.</p></dd>
+<dt class="flush"><code>--ours</code></dt><dd><p>Check out our side (that of the current branch) of the conflict for the
+specified file.</p></dd>
+<dt><code>--theirs</code></dt><dd><p>Check out their side (that of the other branch) of the conflict for the
+specified file.</p></dd>
+<dt><code>--to</code> <var>path</var></dt><dd><p>If the working tree is in a conflicted state, check out the portion of the
+conflict specified by <code>--base</code>, <code>--ours</code>, or <code>--theirs</code> to the given path.</p></dd>
+</dl>
+
+
+<h2 id="EXAMPLES">EXAMPLES</h2>
+
+<ul>
+<li><p>Checkout all files that are missing or placeholders</p>
+
+<p><code>git lfs checkout</code></p></li>
+<li><p>Checkout a specific couple of files</p>
+
+<p><code>git lfs checkout path/to/file1.png path/to.file2.png</code></p></li>
+</ul>
+
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><span class="man-ref">git-lfs-fetch<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-pull<span class="s">(1)</span></span>.</p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-checkout(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-clean.1

@@ -0,0 +1,25 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-CLEAN" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-clean\fR \- Git clean filter that converts large files to pointers
+.
+.SH "SYNOPSIS"
+\fBgit lfs clean\fR \fIpath\fR
+.
+.SH "DESCRIPTION"
+Read the contents of a large file from standard input, and write a Git LFS pointer file for that file to standard output\.
+.
+.P
+Clean is typically run by Git\'s clean filter, configured by the repository\'s Git attributes\.
+.
+.P
+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\.
+.
+.SH "SEE ALSO"
+git\-lfs\-install(1), git\-lfs\-push(1), git\-lfs\-pointer(1), gitattributes(5)\.
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-clean.1.html

@@ -0,0 +1,104 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-clean(1) - Git clean filter that converts large files to pointers</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-clean(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-clean(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-clean</code> - <span class="man-whatis">Git clean filter that converts large files to pointers</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs clean</code> <var>path</var></p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Read the contents of a large file from standard input, and write a Git
+LFS pointer file for that file to standard output.</p>
+
+<p>Clean is typically run by Git's clean filter, configured by the repository's
+Git attributes.</p>
+
+<p>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 <span class="man-ref">git-lfs-pointer<span class="s">(1)</span></span>
+command.</p>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><span class="man-ref">git-lfs-install<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-push<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-pointer<span class="s">(1)</span></span>, <span class="man-ref">gitattributes<span class="s">(5)</span></span>.</p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-clean(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-clone.1

@@ -0,0 +1,49 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-CLONE" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-clone\fR \- Efficiently clone a LFS\-enabled repository
+.
+.SH "SYNOPSIS"
+\fBgit lfs clone\fR [git clone options] \fIrepository\fR [\fIdirectory\fR]
+.
+.SH "DESCRIPTION"
+Clone an LFS enabled Git repository more efficiently by disabling LFS during the git clone, then performing a \'git lfs pull\' directly afterwards\.
+.
+.P
+\'git lfs clone\' also installs all of the repo\-level hooks (\.git/hooks) that LFS requires to operate\. If \fB\-\-separate\-git\-dir\fR is given, the hooks will be installed there\.
+.
+.P
+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\'\.
+.
+.SH "OPTIONS"
+All options supported by \'git clone\'
+.
+.TP
+\fB\-I\fR \fIpaths\fR \fB\-\-include=\fR\fIpaths\fR
+See \fIINCLUDE AND EXCLUDE\fR
+.
+.TP
+\fB\-X\fR \fIpaths\fR \fB\-\-exclude=\fR\fIpaths\fR
+See \fIINCLUDE AND EXCLUDE\fR
+.
+.TP
+\fB\-\-skip\-repo\fR
+Skip installing repo\-level hooks (\.git/hooks) that LFS requires\. Disabled by default\.
+.
+.SH "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\.
+.
+.P
+In lfsconfig, set lfs\.fetchinclude and lfs\.fetchexclude to comma\-separated lists of paths to include/exclude in the fetch (wildcard matching as per gitignore)\. Only paths which are matched by fetchinclude and not matched by fetchexclude will have objects fetched for them\.
+.
+.P
+Note that using the command\-line options \fB\-I\fR and \fB\-X\fR override the respective configuration settings\.
+.
+.SH "SEE ALSO"
+git\-clone(1), git\-lfs\-pull(1)\.
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-clone.1.html

@@ -0,0 +1,134 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-clone(1) - Efficiently clone a LFS-enabled repository</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#OPTIONS">OPTIONS</a>
+    <a href="#INCLUDE-AND-EXCLUDE">INCLUDE AND EXCLUDE</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-clone(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-clone(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-clone</code> - <span class="man-whatis">Efficiently clone a LFS-enabled repository</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs clone</code> [git clone options] <var>repository</var> [<var>directory</var>]</p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Clone an LFS enabled Git repository more efficiently by disabling LFS during the
+git clone, then performing a 'git lfs pull' directly afterwards.</p>
+
+<p>'git lfs clone' also installs all of the repo-level hooks (.git/hooks) that LFS
+requires to operate. If <code>--separate-git-dir</code> is given, the hooks will be
+installed there.</p>
+
+<p>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'.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<p>All options supported by 'git clone'</p>
+
+<dl>
+<dt><code>-I</code> <var>paths</var> <code>--include=</code><var>paths</var></dt><dd><p>See <a href="#INCLUDE-AND-EXCLUDE" title="INCLUDE AND EXCLUDE" data-bare-link="true">INCLUDE AND EXCLUDE</a></p></dd>
+<dt><code>-X</code> <var>paths</var> <code>--exclude=</code><var>paths</var></dt><dd><p>See <a href="#INCLUDE-AND-EXCLUDE" title="INCLUDE AND EXCLUDE" data-bare-link="true">INCLUDE AND EXCLUDE</a></p></dd>
+<dt><code>--skip-repo</code></dt><dd><p>Skip installing repo-level hooks (.git/hooks) that LFS requires. Disabled by
+default.</p></dd>
+</dl>
+
+
+<h2 id="INCLUDE-AND-EXCLUDE">INCLUDE AND EXCLUDE</h2>
+
+<p>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.</p>
+
+<p>In lfsconfig, set lfs.fetchinclude and lfs.fetchexclude to comma-separated lists
+of paths to include/exclude in the fetch (wildcard matching as per gitignore).
+Only paths which are matched by fetchinclude and not matched by fetchexclude
+will have objects fetched for them.</p>
+
+<p>Note that using the command-line options <code>-I</code> and <code>-X</code> override the respective
+configuration settings.</p>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><span class="man-ref">git-clone<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-pull<span class="s">(1)</span></span>.</p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-clone(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-config.5

@@ -0,0 +1,477 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-CONFIG" "5" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-config\fR \- Configuration options for git\-lfs
+.
+.SH "CONFIGURATION FILES"
+git\-lfs reads its configuration from any file supported by \fBgit config \-l\fR, including all per\-repository, per\-user, and per\-system Git configuration files\.
+.
+.P
+Additionally, a small number of settings can be specified in a file called \fB\.lfsconfig\fR at the root of the repository; see the "LFSCONFIG" section for more details\. This configuration file is useful for setting options such as the LFS URL or access type for all users of a repository, especially when these differ from the default\. The \fB\.lfsconfig\fR file uses the same format as \fB\.gitconfig\fR\.
+.
+.P
+If the \fB\.lfsconfig\fR file is missing, the index is checked for a version of the file, and that is used instead\. If both are missing, \fBHEAD\fR is checked for the file\. If the repository is bare, only \fBHEAD\fR is checked\. This order may change for checkouts in the future to better match Git\'s behavior\.
+.
+.P
+Settings from Git configuration files override the \fB\.lfsconfig\fR file\. This allows you to override settings like \fBlfs\.url\fR in your local environment without having to modify the \fB\.lfsconfig\fR file\.
+.
+.P
+Most options regarding git\-lfs are contained in the \fB[lfs]\fR section, meaning they are all named \fBlfs\.foo\fR or similar, although occasionally an lfs option can be scoped inside the configuration for a remote\.
+.
+.SH "LIST OF OPTIONS"
+.
+.SS "General settings"
+.
+.IP "\(bu" 4
+\fBlfs\.url\fR / \fBremote\.<remote>\.lfsurl\fR
+.
+.IP
+The url used to call the Git LFS remote API\. Default blank (derive from clone URL)\.
+.
+.IP "\(bu" 4
+\fBlfs\.pushurl\fR / \fBremote\.<remote>\.lfspushurl\fR
+.
+.IP
+The url used to call the Git LFS remote API when pushing\. Default blank (derive from either LFS non\-push urls or clone url)\.
+.
+.IP "\(bu" 4
+\fBremote\.lfsdefault\fR
+.
+.IP
+The remote used to find the Git LFS remote API\. \fBlfs\.url\fR and \fBbranch\.*\.remote\fR for the current branch override this setting\. If this setting is not specified and there is exactly one remote, that remote is picked; otherwise, the default is \fBorigin\fR\.
+.
+.IP "\(bu" 4
+\fBremote\.lfspushdefault\fR
+.
+.IP
+The remote used to find the Git LFS remote API when pushing\. \fBlfs\.url\fR and \fBbranch\.*\.pushremote\fR for the current branch override this setting\. If this setting is not set, \fBremote\.pushdefault\fR is used, or if that is not set, the order of selection is used as specified in the \fBremote\.lfsdefault\fR above\.
+.
+.IP "\(bu" 4
+\fBlfs\.dialtimeout\fR
+.
+.IP
+Sets the maximum time, in seconds, that the HTTP client will wait to initiate a connection\. This does not include the time to send a request and wait for a response\. Default: 30 seconds
+.
+.IP "\(bu" 4
+\fBlfs\.tlstimeout\fR
+.
+.IP
+Sets the maximum time, in seconds, that the HTTP client will wait for a TLS handshake\. Default: 30 seconds\.
+.
+.IP "\(bu" 4
+\fBlfs\.activitytimeout\fR / \fBlfs\.https://<host>\.activitytimeout\fR
+.
+.IP
+Sets the maximum time, in seconds, that the HTTP client will wait for the next tcp read or write\. If < 1, no activity timeout is used at all\. Default: 30 seconds
+.
+.IP "\(bu" 4
+\fBlfs\.keepalive\fR
+.
+.IP
+Sets the maximum time, in seconds, for the HTTP client to maintain keepalive connections\. Default: 30 minutes\.
+.
+.IP "\(bu" 4
+\fBlfs\.ssh\.automultiplex\fR
+.
+.IP
+When using the pure SSH\-based protocol, whether to multiplex requests over a single connection when possible\. This option requires the use of OpenSSH or a compatible SSH client\. Default: true\.
+.
+.IP "\(bu" 4
+\fBlfs\.ssh\.retries\fR
+.
+.IP
+Specifies the number of times Git LFS will attempt to obtain authorization via SSH before aborting\. Default: 5\.
+.
+.IP "\(bu" 4
+\fBcore\.askpass\fR, GIT_ASKPASS
+.
+.IP
+Given as a program and its arguments, this is invoked when authentication is needed against the LFS API\. The contents of stdout are interpreted as the password\.
+.
+.IP "\(bu" 4
+\fBlfs\.cachecredentials\fR
+.
+.IP
+Enables in\-memory SSH and Git Credential caching for a single \'git lfs\' command\. Default: enabled\.
+.
+.IP "\(bu" 4
+\fBlfs\.storage\fR
+.
+.IP
+Allow override LFS storage directory\. Non\-absolute path is relativized to inside of Git repository directory (usually \fB\.git\fR)\.
+.
+.IP
+Note: you should not run \fBgit lfs prune\fR if you have different repositories sharing the same storage directory\.
+.
+.IP
+Default: \fBlfs\fR in Git repository directory (usually \fB\.git/lfs\fR)\.
+.
+.IP "\(bu" 4
+\fBlfs\.largefilewarning\fR
+.
+.IP
+Warn when a file is 4 GiB or larger\. Such files will be corrupted when using Windows (unless smudging is disabled) due to a limitation in Git\. Default: true\.
+.
+.IP "" 0
+.
+.SS "Transfer (upload / download) settings"
+These settings control how the upload and download of LFS content occurs\.
+.
+.IP "\(bu" 4
+\fBlfs\.concurrenttransfers\fR
+.
+.IP
+The number of concurrent uploads/downloads\. Default 8\.
+.
+.IP "\(bu" 4
+\fBlfs\.basictransfersonly\fR
+.
+.IP
+If set to true, only basic HTTP upload/download transfers will be used, ignoring any more advanced transfers that the client/server may support\. This is primarily to work around bugs or incompatibilities\.
+.
+.IP
+The git\-lfs client supports basic HTTP downloads, resumable HTTP downloads (using \fBRange\fR headers), and resumable uploads via tus\.io protocol\. Custom transfer methods can be added via \fBlfs\.customtransfer\fR (see next section)\. However setting this value to true limits the client to simple HTTP\.
+.
+.IP "\(bu" 4
+\fBlfs\.tustransfers\fR
+.
+.IP
+If set to true, this enables resumable uploads of LFS objects through the tus\.io API\. Once this feature is finalized, this setting will be removed, and tus\.io uploads will be available for all clients\.
+.
+.IP "\(bu" 4
+\fBlfs\.standalonetransferagent\fR
+.
+.IP
+Allows the specified custom transfer agent to be used directly for transferring files, without asking the server how the transfers should be made\. The custom transfer agent has to be defined in a \fBlfs\.customtransfer\.<name>\fR settings group\.
+.
+.IP "\(bu" 4
+\fBlfs\.customtransfer\.<name>\.path\fR
+.
+.IP
+\fBlfs\.customtransfer\.<name>\fR is a settings group which defines a custom transfer hook which allows you to upload/download via an intermediate process, using any mechanism you like (rather than just HTTP)\. \fBpath\fR should point to the process you wish to invoke\. The protocol between the git\-lfs client and the custom transfer process is documented at https://github\.com/git\-lfs/git\-lfs/blob/main/docs/custom\-transfers\.md
+.
+.IP
+\fIname\fR must be a unique identifier that the LFS server understands\. When calling the LFS API the client will include a list of supported transfer types\. If the server also supports this named transfer type, it will select it and actions returned from the API will be in relation to that transfer type (may not be traditional URLs for example)\. Only if the server accepts \fIname\fR as a transfer it supports will this custom transfer process be invoked\.
+.
+.IP "\(bu" 4
+\fBlfs\.customtransfer\.<name>\.args\fR
+.
+.IP
+If the custom transfer process requires any arguments, these can be provided here\. This string will be expanded by the shell\.
+.
+.IP "\(bu" 4
+\fBlfs\.customtransfer\.<name>\.concurrent\fR
+.
+.IP
+If true (the default), git\-lfs will invoke the custom transfer process multiple times in parallel, according to \fBlfs\.concurrenttransfers\fR, splitting the transfer workload between the processes\.
+.
+.IP "\(bu" 4
+\fBlfs\.customtransfer\.<name>\.direction\fR
+.
+.IP
+Specifies which direction the custom transfer process supports, either "download", "upload", or "both"\. The default if unspecified is "both"\.
+.
+.IP "\(bu" 4
+\fBlfs\.transfer\.maxretries\fR
+.
+.IP
+Specifies how many retries LFS will attempt per OID before marking the transfer as failed\. Must be an integer which is at least one\. If the value is not an integer, is less than one, or is not given, a value of eight will be used instead\.
+.
+.IP "\(bu" 4
+\fBlfs\.transfer\.maxretrydelay\fR
+.
+.IP
+Specifies the maximum time in seconds LFS will wait between each retry attempt\. LFS uses exponential backoff for retries, doubling the time between each retry until reaching this limit\. If a server requests a delay using the \fBRetry\-After\fR header, the header value overrides the exponential delay for that attempt and is not limited by this option\.
+.
+.IP
+Must be an integer which is not negative\. Use zero to disable delays between retries unless requested by a server\. If the value is not an integer, is negative, or is not given, a value of ten will be used instead\.
+.
+.IP "\(bu" 4
+\fBlfs\.transfer\.maxverifies\fR
+.
+.IP
+Specifies how many verification requests LFS will attempt per OID before marking the transfer as failed, if the object has a verification action associated with it\. Must be an integer which is at least one\. If the value is not an integer, is less than one, or is not given, a default value of three will be used instead\.
+.
+.IP "\(bu" 4
+\fBlfs\.transfer\.enablehrefrewrite\fR
+.
+.IP
+If set to true, this enables rewriting href of LFS objects using \fBurl\.*\.insteadof/pushinsteadof\fR config\. \fBpushinsteadof\fR is used only for uploading, and \fBinsteadof\fR is used for downloading and for uploading when \fBpushinsteadof\fR is not set\.
+.
+.IP "" 0
+.
+.SS "Push settings"
+.
+.IP "\(bu" 4
+\fBlfs\.allowincompletepush\fR
+.
+.IP
+When pushing, allow objects to be missing from the local cache without halting a Git push\. Default: false\.
+.
+.IP "" 0
+.
+.SS "Fetch settings"
+.
+.IP "\(bu" 4
+\fBlfs\.fetchinclude\fR
+.
+.IP
+When fetching, only download objects which match any entry on this comma\-separated list of paths/filenames\. Wildcard matching is as per git\-ignore(1)\. See git\-lfs\-fetch(1) for examples\.
+.
+.IP "\(bu" 4
+\fBlfs\.fetchexclude\fR
+.
+.IP
+When fetching, do not download objects which match any item on this comma\-separated list of paths/filenames\. Wildcard matching is as per git\-ignore(1)\. See git\-lfs\-fetch(1) for examples\.
+.
+.IP "\(bu" 4
+\fBlfs\.fetchrecentrefsdays\fR
+.
+.IP
+If non\-zero, fetches refs which have commits within N days of the current date\. Only local refs are included unless lfs\.fetchrecentremoterefs is true\. Also used as a basis for pruning old files\. The default is 7 days\.
+.
+.IP "\(bu" 4
+\fBlfs\.fetchrecentremoterefs\fR
+.
+.IP
+If true, fetches remote refs (for the remote you\'re fetching) as well as local refs in the recent window\. This is useful to fetch objects for remote branches you might want to check out later\. The default is true; if you set this to false, fetching for those branches will only occur when you either check them out (losing the advantage of fetch \-\-recent), or create a tracking local branch separately then fetch again\.
+.
+.IP "\(bu" 4
+\fBlfs\.fetchrecentcommitsdays\fR
+.
+.IP
+In addition to fetching at refs, also fetches previous changes made within N days of the latest commit on the ref\. This is useful if you\'re often reviewing recent changes\. Also used as a basis for pruning old files\. The default is 0 (no previous changes)\.
+.
+.IP "\(bu" 4
+\fBlfs\.fetchrecentalways\fR
+.
+.IP
+Always operate as if \-\-recent was included in a \fBgit lfs fetch\fR call\. Default false\.
+.
+.IP "" 0
+.
+.SS "Prune settings"
+.
+.IP "\(bu" 4
+\fBlfs\.pruneoffsetdays\fR
+.
+.IP
+The number of days added to the \fBlfs\.fetchrecent*\fR settings to determine what can be pruned\. Default is 3 days, i\.e\. that anything fetched at the very oldest edge of the \'recent window\' is eligible for pruning 3 days later\.
+.
+.IP "\(bu" 4
+\fBlfs\.pruneremotetocheck\fR
+.
+.IP
+Set the remote that LFS files must have been pushed to in order for them to be considered eligible for local pruning\. Also the remote which is called if \-\-verify\-remote is enabled\.
+.
+.IP "\(bu" 4
+\fBlfs\.pruneverifyremotealways\fR
+.
+.IP
+Always run \fBgit lfs prune\fR as if \fB\-\-verify\-remote\fR was provided\.
+.
+.IP "" 0
+.
+.SS "Extensions"
+.
+.IP "\(bu" 4
+\fBlfs\.extension\.<name>\.<setting>\fR
+.
+.IP
+Git LFS extensions enable the manipulation of files streams during smudge and clean\. \fBname\fR groups the settings for a single extension, and the settings are:
+.
+.IP "\(bu" 4
+\fBclean\fR The command which runs when files are added to the index
+.
+.IP "\(bu" 4
+\fBsmudge\fR The command which runs when files are written to the working copy
+.
+.IP "\(bu" 4
+\fBpriority\fR The order of this extension compared to others
+.
+.IP "" 0
+
+.
+.IP "" 0
+.
+.SS "Other settings"
+.
+.IP "\(bu" 4
+\fBlfs\.<url>\.access\fR
+.
+.IP
+Note: this setting is normally set by LFS itself on receiving a 401 response (authentication required), you don\'t normally need to set it manually\.
+.
+.IP
+If set to "basic" then credentials will be requested before making batch requests to this url, otherwise a public request will initially be attempted\.
+.
+.IP "\(bu" 4
+\fBlfs\.<url>\.locksverify\fR
+.
+.IP
+Determines whether locks are checked before Git pushes\. This prevents you from pushing changes to files that other users have locked\. The Git LFS pre\-push hook varies its behavior based on the value of this config key\.
+.
+.IP "\(bu" 4
+\fBnull\fR \- In the absence of a value, Git LFS will attempt the call, and warn if it returns an error\. If the response is valid, Git LFS will set the value to \fBtrue\fR, and will halt the push if the user attempts to update a file locked by another user\. If the server returns a \fB501 Not Implemented\fR response, Git LFS will set the value to \fBfalse\.\fR
+.
+.IP "\(bu" 4
+\fBtrue\fR \- Git LFS will attempt to verify locks, halting the Git push if there are any server issues, or if the user attempts to update a file locked by another user\.
+.
+.IP "\(bu" 4
+\fBfalse\fR \- Git LFS will completely skip the lock check in the pre\-push hook\. You should set this if you\'re not using File Locking, or your Git server verifies locked files on pushes automatically\.
+.
+.IP "" 0
+.
+.IP
+Supports URL config lookup as described in: https://git\-scm\.com/docs/git\-config#git\-config\-httplturlgt\. To set this value per\-host: \fBgit config \-\-global lfs\.https://github\.com/\.locksverify [true|false]\fR\.
+.
+.IP "\(bu" 4
+\fBlfs\.<url>\.contenttype\fR
+.
+.IP
+Determines whether Git LFS should attempt to detect an appropriate HTTP \fBContent\-Type\fR header when uploading using the \'basic\' upload adapter\. If set to false, the default header of \fBContent\-Type: application/octet\-stream\fR is chosen instead\. Default: \'true\'\.
+.
+.IP "\(bu" 4
+\fBlfs\.skipdownloaderrors\fR
+.
+.IP
+Causes Git LFS not to abort the smudge filter when a download error is encountered, which allows actions such as checkout to work when you are unable to download the LFS content\. LFS files which could not download will contain pointer content instead\.
+.
+.IP
+Note that this will result in git commands which call the smudge filter to report success even in cases when LFS downloads fail, which may affect scripts\.
+.
+.IP
+You can also set the environment variable GIT_LFS_SKIP_DOWNLOAD_ERRORS=1 to get the same effect\.
+.
+.IP "\(bu" 4
+\fBGIT_LFS_PROGRESS\fR
+.
+.IP
+This environment variable causes Git LFS to emit progress updates to an absolute file\-path on disk when cleaning, smudging, or fetching\.
+.
+.IP
+Progress is reported periodically in the form of a new line being appended to the end of the file\. Each new line will take the following format:
+.
+.IP
+\fB<direction> <current>/<total files> <downloaded>/<total> <name>\fR
+.
+.IP
+Each field is described below:
+.
+.IP "\(bu" 4
+\fBdirection\fR: The direction of transfer, either "checkout", "download", or "upload"\.
+.
+.IP "\(bu" 4
+\fBcurrent\fR The index of the currently transferring file\.
+.
+.IP "\(bu" 4
+\fBtotal files\fR The estimated count of all files to be transferred\.
+.
+.IP "\(bu" 4
+\fBdownloaded\fR The number of bytes already downloaded\.
+.
+.IP "\(bu" 4
+\fBtotal\fR The entire size of the file, in bytes\.
+.
+.IP "\(bu" 4
+\fBname\fR The name of the file\.
+.
+.IP "" 0
+
+.
+.IP "\(bu" 4
+\fBGIT_LFS_FORCE_PROGRESS\fR \fBlfs\.forceprogress\fR
+.
+.IP
+Controls whether Git LFS will suppress progress status when the standard output stream is not attached to a terminal\. The default is \fBfalse\fR which makes Git LFS detect whether stdout is a terminal and suppress progress when it\'s not; you can disable this behaviour and force progress status even when standard output stream is not a terminal by setting either variable to 1, \'yes\' or \'true\'\.
+.
+.IP "\(bu" 4
+\fBGIT_LFS_SKIP_SMUDGE\fR
+.
+.IP
+Sets whether or not Git LFS will skip attempting to convert pointers of files tracked into their corresponding objects when checked out into a working copy\. If \'true\', \'1\', \'on\', or similar, Git LFS will skip the smudge process in both \fBgit lfs smudge\fR and \fBgit lfs filter\-process\fR\. If unset, or set to \'false\', \'0\', \'off\', or similar, Git LFS will smudge files as normal\.
+.
+.IP "\(bu" 4
+\fBGIT_LFS_SKIP_PUSH\fR
+.
+.IP
+Sets whether or not Git LFS will attempt to upload new Git LFS object in a pre\-push hook\. If \'true\', \'1\', \'on\', or similar, Git LFS will skip the pre\-push hook, so no new Git LFS objects will be uploaded\. If unset, or set to \'false\', \'0\', \'off\', or similar, Git LFS will proceed as normal\.
+.
+.IP "\(bu" 4
+\fBGIT_LFS_SET_LOCKABLE_READONLY\fR \fBlfs\.setlockablereadonly\fR
+.
+.IP
+These settings, the first an environment variable and the second a gitconfig setting, control whether files marked as \'lockable\' in \fBgit lfs track\fR are made read\-only in the working copy when not locked by the current user\. The default is \fBtrue\fR; you can disable this behaviour and have all files writeable by setting either variable to 0, \'no\' or \'false\'\.
+.
+.IP "\(bu" 4
+\fBlfs\.lockignoredfiles\fR
+.
+.IP
+This setting controls whether Git LFS will set ignored files that match the lockable pattern read only as well as tracked files\. The default is \fBfalse\fR; you can enable this behavior by setting the variable to 1, \'yes\', or \'true\'\.
+.
+.IP "\(bu" 4
+\fBlfs\.defaulttokenttl\fR
+.
+.IP
+This setting sets a default token TTL when git\-lfs\-authenticate does not include the TTL in the JSON response but still enforces it\.
+.
+.IP
+Note that this is only necessary for larger repositories hosted on LFS servers that don\'t include the TTL\.
+.
+.IP "" 0
+.
+.SH "LFSCONFIG"
+The \.lfsconfig file in a repository is read and interpreted in the same format as the file stored in \.git/config\. It allows a subset of keys to be used, including and limited to:
+.
+.IP "\(bu" 4
+lfs\.allowincompletepush
+.
+.IP "\(bu" 4
+lfs\.fetchexclude
+.
+.IP "\(bu" 4
+lfs\.fetchinclude
+.
+.IP "\(bu" 4
+lfs\.gitprotocol
+.
+.IP "\(bu" 4
+lfs\.locksverify
+.
+.IP "\(bu" 4
+lfs\.pushurl
+.
+.IP "\(bu" 4
+lfs\.skipdownloaderrors
+.
+.IP "\(bu" 4
+lfs\.url
+.
+.IP "\(bu" 4
+lfs\.{*}\.access
+.
+.IP "\(bu" 4
+remote\.{name}\.lfsurl
+.
+.IP "" 0
+.
+.P
+The set of keys allowed in this file is restricted for security reasons\.
+.
+.SH "EXAMPLES"
+.
+.TP
+Configure a custom LFS endpoint for your repository:
+
+.
+.P
+\fBgit config \-f \.lfsconfig lfs\.url https://lfs\.example\.com/foo/bar/info/lfs\fR
+.
+.SH "SEE ALSO"
+git\-config(1), git\-lfs\-install(1), gitattributes(5)
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-config.5.html

@@ -0,0 +1,520 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-config(5) - Configuration options for git-lfs</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#CONFIGURATION-FILES">CONFIGURATION FILES</a>
+    <a href="#LIST-OF-OPTIONS">LIST OF OPTIONS</a>
+    <a href="#LFSCONFIG">LFSCONFIG</a>
+    <a href="#EXAMPLES">EXAMPLES</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-config(5)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-config(5)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-config</code> - <span class="man-whatis">Configuration options for git-lfs</span>
+</p>
+
+<h2 id="CONFIGURATION-FILES">CONFIGURATION FILES</h2>
+
+<p>git-lfs reads its configuration from any file supported by <code>git config -l</code>,
+including all per-repository, per-user, and per-system Git configuration files.</p>
+
+<p>Additionally, a small number of settings can be specified in a file called
+<code>.lfsconfig</code> at the root of the repository; see the "LFSCONFIG" section for more
+details. This configuration file is useful for setting options such as the LFS
+URL or access type for all users of a repository, especially when these differ
+from the default. The <code>.lfsconfig</code> file uses the same format as <code>.gitconfig</code>.</p>
+
+<p>If the <code>.lfsconfig</code> file is missing, the index is checked for a version of the
+file, and that is used instead.  If both are missing, <code>HEAD</code> is checked for the
+file.  If the repository is bare, only <code>HEAD</code> is checked.  This order may change
+for checkouts in the future to better match Git's behavior.</p>
+
+<p>Settings from Git configuration files override the <code>.lfsconfig</code> file. This
+allows you to override settings like <code>lfs.url</code> in your local environment without
+having to modify the <code>.lfsconfig</code> file.</p>
+
+<p>Most options regarding git-lfs are contained in the <code>[lfs]</code> section, meaning
+they are all named <code>lfs.foo</code> or similar, although occasionally an lfs option can
+be scoped inside the configuration for a remote.</p>
+
+<h2 id="LIST-OF-OPTIONS">LIST OF OPTIONS</h2>
+
+<h3 id="General-settings">General settings</h3>
+
+<ul>
+<li><p><code>lfs.url</code> / <code>remote.&lt;remote>.lfsurl</code></p>
+
+<p>The url used to call the Git LFS remote API. Default blank (derive from clone
+URL).</p></li>
+<li><p><code>lfs.pushurl</code> / <code>remote.&lt;remote>.lfspushurl</code></p>
+
+<p>The url used to call the Git LFS remote API when pushing. Default blank (derive
+from either LFS non-push urls or clone url).</p></li>
+<li><p><code>remote.lfsdefault</code></p>
+
+<p>The remote used to find the Git LFS remote API.  <code>lfs.url</code> and
+<code>branch.*.remote</code> for the current branch override this setting.  If this
+setting is not specified and there is exactly one remote, that remote is
+picked; otherwise, the default is <code>origin</code>.</p></li>
+<li><p><code>remote.lfspushdefault</code></p>
+
+<p>The remote used to find the Git LFS remote API when pushing.  <code>lfs.url</code> and
+<code>branch.*.pushremote</code> for the current branch override this setting.  If this
+setting is not set, <code>remote.pushdefault</code> is used, or if that is not set, the
+order of selection is used as specified in the <code>remote.lfsdefault</code> above.</p></li>
+<li><p><code>lfs.dialtimeout</code></p>
+
+<p>Sets the maximum time, in seconds, that the HTTP client will wait to initiate
+a connection. This does not include the time to send a request and wait for a
+response. Default: 30 seconds</p></li>
+<li><p><code>lfs.tlstimeout</code></p>
+
+<p>Sets the maximum time, in seconds, that the HTTP client will wait for a TLS
+handshake. Default: 30 seconds.</p></li>
+<li><p><code>lfs.activitytimeout</code> / <code>lfs.https://&lt;host>.activitytimeout</code></p>
+
+<p>Sets the maximum time, in seconds, that the HTTP client will wait for the
+next tcp read or write. If &lt; 1, no activity timeout is used at all.
+Default: 30 seconds</p></li>
+<li><p><code>lfs.keepalive</code></p>
+
+<p>Sets the maximum time, in seconds, for the HTTP client to maintain keepalive
+connections. Default: 30 minutes.</p></li>
+<li><p><code>lfs.ssh.automultiplex</code></p>
+
+<p>When using the pure SSH-based protocol, whether to multiplex requests over a
+single connection when possible.  This option requires the use of OpenSSH or a
+compatible SSH client.  Default: true.</p></li>
+<li><p><code>lfs.ssh.retries</code></p>
+
+<p>Specifies the number of times Git LFS will attempt to obtain authorization via
+SSH before aborting. Default: 5.</p></li>
+<li><p><code>core.askpass</code>, GIT_ASKPASS</p>
+
+<p>Given as a program and its arguments, this is invoked when authentication is
+needed against the LFS API. The contents of stdout are interpreted as the
+password.</p></li>
+<li><p><code>lfs.cachecredentials</code></p>
+
+<p>Enables in-memory SSH and Git Credential caching for a single 'git lfs'
+command. Default: enabled.</p></li>
+<li><p><code>lfs.storage</code></p>
+
+<p>Allow override LFS storage directory. Non-absolute path is relativized to
+inside of Git repository directory (usually <code>.git</code>).</p>
+
+<p>Note: you should not run <code>git lfs prune</code> if you have different repositories
+sharing the same storage directory.</p>
+
+<p>Default: <code>lfs</code> in Git repository directory (usually <code>.git/lfs</code>).</p></li>
+<li><p><code>lfs.largefilewarning</code></p>
+
+<p>Warn when a file is 4 GiB or larger. Such files will be corrupted when using
+Windows (unless smudging is disabled) due to a limitation in Git.  Default:
+true.</p></li>
+</ul>
+
+
+<h3 id="Transfer-upload-download-settings">Transfer (upload / download) settings</h3>
+
+<p>  These settings control how the upload and download of LFS content occurs.</p>
+
+<ul>
+<li><p><code>lfs.concurrenttransfers</code></p>
+
+<p>The number of concurrent uploads/downloads. Default 8.</p></li>
+<li><p><code>lfs.basictransfersonly</code></p>
+
+<p>If set to true, only basic HTTP upload/download transfers will be used,
+ignoring any more advanced transfers that the client/server may support.
+This is primarily to work around bugs or incompatibilities.</p>
+
+<p>The git-lfs client supports basic HTTP downloads, resumable HTTP downloads
+(using <code>Range</code> headers), and resumable uploads via tus.io protocol. Custom
+transfer methods can be added via <code>lfs.customtransfer</code> (see next section).
+However setting this value to true limits the client to simple HTTP.</p></li>
+<li><p><code>lfs.tustransfers</code></p>
+
+<p>If set to true, this enables resumable uploads of LFS objects through the
+tus.io API. Once this feature is finalized, this setting will be removed,
+and tus.io uploads will be available for all clients.</p></li>
+<li><p><code>lfs.standalonetransferagent</code></p>
+
+<p>Allows the specified custom transfer agent to be used directly
+for transferring files, without asking the server how the transfers
+should be made. The custom transfer agent has to be defined in a
+<code>lfs.customtransfer.&lt;name></code> settings group.</p></li>
+<li><p><code>lfs.customtransfer.&lt;name>.path</code></p>
+
+<p><code>lfs.customtransfer.&lt;name></code> is a settings group which defines a custom
+transfer hook which allows you to upload/download via an intermediate process,
+using any mechanism you like (rather than just HTTP). <code>path</code> should point to
+the process you wish to invoke. The protocol between the git-lfs client and
+the custom transfer process is documented at
+https://github.com/git-lfs/git-lfs/blob/main/docs/custom-transfers.md</p>
+
+<p><var>name</var> must be a unique identifier that the LFS server understands. When
+calling the LFS API the client will include a list of supported transfer
+types. If the server also supports this named transfer type, it will select it
+and actions returned from the API will be in relation to that transfer type
+(may not be traditional URLs for example). Only if the server accepts <var>name</var>
+as a transfer it supports will this custom transfer process be invoked.</p></li>
+<li><p><code>lfs.customtransfer.&lt;name>.args</code></p>
+
+<p>If the custom transfer process requires any arguments, these can be provided
+here.  This string will be expanded by the shell.</p></li>
+<li><p><code>lfs.customtransfer.&lt;name>.concurrent</code></p>
+
+<p>If true (the default), git-lfs will invoke the custom transfer process
+multiple times in parallel, according to <code>lfs.concurrenttransfers</code>, splitting
+the transfer workload between the processes.</p></li>
+<li><p><code>lfs.customtransfer.&lt;name>.direction</code></p>
+
+<p>Specifies which direction the custom transfer process supports, either
+"download", "upload", or "both". The default if unspecified is "both".</p></li>
+<li><p><code>lfs.transfer.maxretries</code></p>
+
+<p>Specifies how many retries LFS will attempt per OID before marking the
+transfer as failed. Must be an integer which is at least one. If the value is
+not an integer, is less than one, or is not given, a value of eight will be
+used instead.</p></li>
+<li><p><code>lfs.transfer.maxretrydelay</code></p>
+
+<p>Specifies the maximum time in seconds LFS will wait between each retry
+attempt. LFS uses exponential backoff for retries, doubling the time between
+each retry until reaching this limit. If a server requests a delay using the
+<code>Retry-After</code> header, the header value overrides the exponential delay for
+that attempt and is not limited by this option.</p>
+
+<p>Must be an integer which is not negative. Use zero to disable delays between
+retries unless requested by a server. If the value is not an integer, is
+negative, or is not given, a value of ten will be used instead.</p></li>
+<li><p><code>lfs.transfer.maxverifies</code></p>
+
+<p>Specifies how many verification requests LFS will attempt per OID before
+marking the transfer as failed, if the object has a verification action
+associated with it. Must be an integer which is at least one. If the value is
+not an integer, is less than one, or is not given, a default value of three
+will be used instead.</p></li>
+<li><p><code>lfs.transfer.enablehrefrewrite</code></p>
+
+<p>If set to true, this enables rewriting href of LFS objects using
+<code>url.*.insteadof/pushinsteadof</code> config. <code>pushinsteadof</code> is used only for
+uploading, and <code>insteadof</code> is used for downloading and for uploading when
+<code>pushinsteadof</code> is not set.</p></li>
+</ul>
+
+
+<h3 id="Push-settings">Push settings</h3>
+
+<ul>
+<li><p><code>lfs.allowincompletepush</code></p>
+
+<p>When pushing, allow objects to be missing from the local cache without halting
+a Git push. Default: false.</p></li>
+</ul>
+
+
+<h3 id="Fetch-settings">Fetch settings</h3>
+
+<ul>
+<li><p><code>lfs.fetchinclude</code></p>
+
+<p>When fetching, only download objects which match any entry on this
+comma-separated list of paths/filenames. Wildcard matching is as per
+<span class="man-ref">git-ignore<span class="s">(1)</span></span>. See <span class="man-ref">git-lfs-fetch<span class="s">(1)</span></span> for examples.</p></li>
+<li><p><code>lfs.fetchexclude</code></p>
+
+<p>When fetching, do not download objects which match any item on this
+comma-separated list of paths/filenames. Wildcard matching is as per
+<span class="man-ref">git-ignore<span class="s">(1)</span></span>. See <span class="man-ref">git-lfs-fetch<span class="s">(1)</span></span> for examples.</p></li>
+<li><p><code>lfs.fetchrecentrefsdays</code></p>
+
+<p>If non-zero, fetches refs which have commits within N days of the current
+date. Only local refs are included unless lfs.fetchrecentremoterefs is true.
+Also used as a basis for pruning old files.
+The default is 7 days.</p></li>
+<li><p><code>lfs.fetchrecentremoterefs</code></p>
+
+<p>If true, fetches remote refs (for the remote you're fetching) as well as local
+refs in the recent window. This is useful to fetch objects for remote branches
+you might want to check out later. The default is true; if you set this to
+false, fetching for those branches will only occur when you either check them
+out (losing the advantage of fetch --recent), or create a tracking local
+branch separately then fetch again.</p></li>
+<li><p><code>lfs.fetchrecentcommitsdays</code></p>
+
+<p>In addition to fetching at refs, also fetches previous changes made within N
+days of the latest commit on the ref. This is useful if you're often reviewing
+recent changes.   Also used as a basis for pruning old files.
+The default is 0 (no previous changes).</p></li>
+<li><p><code>lfs.fetchrecentalways</code></p>
+
+<p>Always operate as if --recent was included in a <code>git lfs fetch</code> call. Default
+false.</p></li>
+</ul>
+
+
+<h3 id="Prune-settings">Prune settings</h3>
+
+<ul>
+<li><p><code>lfs.pruneoffsetdays</code></p>
+
+<p>The number of days added to the <code>lfs.fetchrecent*</code> settings to determine what
+can be pruned. Default is 3 days, i.e. that anything fetched at the very
+oldest edge of the 'recent window' is eligible for pruning 3 days later.</p></li>
+<li><p><code>lfs.pruneremotetocheck</code></p>
+
+<p>Set the remote that LFS files must have been pushed to in order for them to
+be considered eligible for local pruning. Also the remote which is called if
+--verify-remote is enabled.</p></li>
+<li><p><code>lfs.pruneverifyremotealways</code></p>
+
+<p>Always run <code>git lfs prune</code> as if <code>--verify-remote</code> was provided.</p></li>
+</ul>
+
+
+<h3 id="Extensions">Extensions</h3>
+
+<ul>
+<li><p><code>lfs.extension.&lt;name>.&lt;setting></code></p>
+
+<p>Git LFS extensions enable the manipulation of files streams during smudge and
+clean. <code>name</code> groups the settings for a single extension, and the settings
+are:</p>
+
+<ul>
+<li><code>clean</code> The command which runs when files are added to the index</li>
+<li><code>smudge</code> The command which runs when files are written to the working copy</li>
+<li><code>priority</code> The order of this extension compared to others</li>
+</ul>
+</li>
+</ul>
+
+
+<h3 id="Other-settings">Other settings</h3>
+
+<ul>
+<li><p><code>lfs.&lt;url>.access</code></p>
+
+<p>Note: this setting is normally set by LFS itself on receiving a 401 response
+(authentication required), you don't normally need to set it manually.</p>
+
+<p>If set to "basic" then credentials will be requested before making batch
+requests to this url, otherwise a public request will initially be attempted.</p></li>
+<li><p><code>lfs.&lt;url>.locksverify</code></p>
+
+<p>Determines whether locks are checked before Git pushes. This prevents you from
+pushing changes to files that other users have locked. The Git LFS pre-push
+hook varies its behavior based on the value of this config key.</p>
+
+<ul>
+<li><code>null</code> - In the absence of a value, Git LFS will attempt the call, and warn
+if it returns an error. If the response is valid, Git LFS will set the value
+to <code>true</code>, and will halt the push if the user attempts to update a file locked
+by another user. If the server returns a <code>501 Not Implemented</code> response, Git
+LFS will set the value to <code>false.</code></li>
+<li><code>true</code> - Git LFS will attempt to verify locks, halting the Git push if there
+are any server issues, or if the user attempts to update a file locked by
+another user.</li>
+<li><code>false</code> - Git LFS will completely skip the lock check in the pre-push hook.
+You should set this if you're not using File Locking, or your Git server
+verifies locked files on pushes automatically.</li>
+</ul>
+
+
+<p>Supports URL config lookup as described in:
+https://git-scm.com/docs/git-config#git-config-httplturlgt. To set this value
+per-host: <code>git config --global lfs.https://github.com/.locksverify [true|false]</code>.</p></li>
+<li><p><code>lfs.&lt;url>.contenttype</code></p>
+
+<p>Determines whether Git LFS should attempt to detect an appropriate HTTP
+<code>Content-Type</code> header when uploading using the 'basic' upload adapter. If set
+to false, the default header of <code>Content-Type: application/octet-stream</code> is
+chosen instead. Default: 'true'.</p></li>
+<li><p><code>lfs.skipdownloaderrors</code></p>
+
+<p>Causes Git LFS not to abort the smudge filter when a download error is
+encountered, which allows actions such as checkout to work when you are unable
+to download the LFS content. LFS files which could not download will contain
+pointer content instead.</p>
+
+<p>Note that this will result in git commands which call the smudge filter to
+report success even in cases when LFS downloads fail, which may affect
+scripts.</p>
+
+<p>You can also set the environment variable GIT_LFS_SKIP_DOWNLOAD_ERRORS=1 to
+get the same effect.</p></li>
+<li><p><code>GIT_LFS_PROGRESS</code></p>
+
+<p>This environment variable causes Git LFS to emit progress updates to an
+absolute file-path on disk when cleaning, smudging, or fetching.</p>
+
+<p>Progress is reported periodically in the form of a new line being appended to
+the end of the file. Each new line will take the following format:</p>
+
+<p><code>&lt;direction> &lt;current>/&lt;total files> &lt;downloaded>/&lt;total> &lt;name></code></p>
+
+<p>Each field is described below:</p>
+
+<ul>
+<li><code>direction</code>: The direction of transfer, either "checkout", "download", or
+"upload".</li>
+<li><code>current</code> The index of the currently transferring file.</li>
+<li><code>total files</code> The estimated count of all files to be transferred.</li>
+<li><code>downloaded</code> The number of bytes already downloaded.</li>
+<li><code>total</code> The entire size of the file, in bytes.</li>
+<li><code>name</code> The name of the file.</li>
+</ul>
+</li>
+<li><p><code>GIT_LFS_FORCE_PROGRESS</code>
+<code>lfs.forceprogress</code></p>
+
+<p>Controls whether Git LFS will suppress progress status when the standard
+output stream is not attached to a terminal. The default is <code>false</code> which
+makes Git LFS detect whether stdout is a terminal and suppress progress when
+it's not; you can disable this behaviour and force progress status even when
+standard output stream is not a terminal by setting either variable to 1,
+'yes' or 'true'.</p></li>
+<li><p><code>GIT_LFS_SKIP_SMUDGE</code></p>
+
+<p>Sets whether or not Git LFS will skip attempting to convert pointers of files
+tracked into their corresponding objects when checked out into a working copy.
+If 'true', '1', 'on', or similar, Git LFS will skip the smudge process in both
+<code>git lfs smudge</code> and <code>git lfs filter-process</code>. If unset, or set to 'false',
+'0', 'off', or similar, Git LFS will smudge files as normal.</p></li>
+<li><p><code>GIT_LFS_SKIP_PUSH</code></p>
+
+<p>Sets whether or not Git LFS will attempt to upload new Git LFS object in a
+pre-push hook. If 'true', '1', 'on', or similar, Git LFS will skip the
+pre-push hook, so no new Git LFS objects will be uploaded. If unset, or set to
+'false', '0', 'off', or similar, Git LFS will proceed as normal.</p></li>
+<li><p><code>GIT_LFS_SET_LOCKABLE_READONLY</code>
+<code>lfs.setlockablereadonly</code></p>
+
+<p>These settings, the first an environment variable and the second a gitconfig
+setting, control whether files marked as 'lockable' in <code>git lfs track</code> are
+made read-only in the working copy when not locked by the current user.
+The default is <code>true</code>; you can disable this behaviour and have all files
+writeable by setting either variable to 0, 'no' or 'false'.</p></li>
+<li><p><code>lfs.lockignoredfiles</code></p>
+
+<p>This setting controls whether Git LFS will set ignored files that match the
+lockable pattern read only as well as tracked files. The default is <code>false</code>;
+you can enable this behavior by setting the variable to 1, 'yes', or 'true'.</p></li>
+<li><p><code>lfs.defaulttokenttl</code></p>
+
+<p>This setting sets a default token TTL when git-lfs-authenticate does not
+include the TTL in the JSON response but still enforces it.</p>
+
+<p>Note that this is only necessary for larger repositories hosted on LFS
+servers that don't include the TTL.</p></li>
+</ul>
+
+
+<h2 id="LFSCONFIG">LFSCONFIG</h2>
+
+<p>The .lfsconfig file in a repository is read and interpreted in the same format
+as the file stored in .git/config. It allows a subset of keys to be used,
+including and limited to:</p>
+
+<ul>
+<li>lfs.allowincompletepush</li>
+<li>lfs.fetchexclude</li>
+<li>lfs.fetchinclude</li>
+<li>lfs.gitprotocol</li>
+<li>lfs.locksverify</li>
+<li>lfs.pushurl</li>
+<li>lfs.skipdownloaderrors</li>
+<li>lfs.url</li>
+<li>lfs.{*}.access</li>
+<li>remote.{name}.lfsurl</li>
+</ul>
+
+
+<p>The set of keys allowed in this file is restricted for security reasons.</p>
+
+<h2 id="EXAMPLES">EXAMPLES</h2>
+
+<dl>
+<dt>Configure a custom LFS endpoint for your repository:</dt><dd></dd>
+</dl>
+
+
+<p>  <code>git config -f .lfsconfig lfs.url https://lfs.example.com/foo/bar/info/lfs</code></p>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><span class="man-ref">git-config<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-install<span class="s">(1)</span></span>, <span class="man-ref">gitattributes<span class="s">(5)</span></span></p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-config(5)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-env.1

@@ -0,0 +1,16 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-ENV" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-env\fR \- Display the Git LFS environment
+.
+.SH "SYNOPSIS"
+\fBgit lfs env\fR
+.
+.SH "DESCRIPTION"
+Display the current Git LFS environment\.
+.
+.SH "SEE ALSO"
+Part of the git\-lfs(1) suite\.

man/git-lfs-env.1.html

@@ -0,0 +1,94 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-env(1) - Display the Git LFS environment</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-env(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-env(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-env</code> - <span class="man-whatis">Display the Git LFS environment</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs env</code></p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Display the current Git LFS environment.</p>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-env(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-ext.1

@@ -0,0 +1,32 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-EXT" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-ext\fR \- View extension details
+.
+.SH "SYNOPSIS"
+\fBgit lfs ext list\fR [\fIname\fR\.\.\.]
+.
+.SH "DESCRIPTION"
+Git LFS extensions enable the manipulation of files streams during smudge and clean\.
+.
+.SH "EXAMPLES"
+.
+.IP "\(bu" 4
+List details for all extensions
+.
+.IP
+\fBgit lfs ext\fR \fBgit lfs ext list\fR
+.
+.IP "\(bu" 4
+List details for the specified extensions
+.
+.IP
+\fBgit lfs ext list \'foo\' \'bar\'\fR
+.
+.IP "" 0
+.
+.SH "SEE ALSO"
+Part of the git\-lfs(1) suite\.

man/git-lfs-ext.1.html

@@ -0,0 +1,109 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-ext(1) - View extension details</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#EXAMPLES">EXAMPLES</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-ext(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-ext(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-ext</code> - <span class="man-whatis">View extension details</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs ext list</code> [<var>name</var>...]</p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Git LFS extensions enable the manipulation of files streams
+during smudge and clean.</p>
+
+<h2 id="EXAMPLES">EXAMPLES</h2>
+
+<ul>
+<li><p>List details for all extensions</p>
+
+<p>  <code>git lfs ext</code>
+  <code>git lfs ext list</code></p></li>
+<li><p>List details for the specified extensions</p>
+
+<p>  <code>git lfs ext list 'foo' 'bar'</code></p></li>
+</ul>
+
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-ext(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-fetch.1

@@ -0,0 +1,150 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-FETCH" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-fetch\fR \- Download all Git LFS files for a given ref
+.
+.SH "SYNOPSIS"
+\fBgit lfs fetch\fR [options] [\fIremote\fR [\fIref\fR\.\.\.]]
+.
+.SH "DESCRIPTION"
+Download Git LFS objects at the given refs from the specified remote\. See \fIDEFAULT REMOTE\fR and \fIDEFAULT REFS\fR for what happens if you don\'t specify\.
+.
+.P
+This does not update the working copy\.
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-I\fR \fIpaths\fR \fB\-\-include=\fR\fIpaths\fR
+Specify lfs\.fetchinclude just for this invocation; see \fIINCLUDE AND EXCLUDE\fR
+.
+.TP
+\fB\-X\fR \fIpaths\fR \fB\-\-exclude=\fR\fIpaths\fR
+Specify lfs\.fetchexclude just for this invocation; see \fIINCLUDE AND EXCLUDE\fR
+.
+.TP
+\fB\-\-recent\fR
+Download objects referenced by recent branches & commits in addition to those that would otherwise be downloaded\. See \fIRECENT CHANGES\fR
+.
+.TP
+\fB\-\-all\fR
+Download all objects that are referenced by any commit reachable from the refs provided as arguments\. If no refs are provided, then all refs are fetched\. This is primarily for backup and migration purposes\. Cannot be combined with \-\-recent or \-\-include/\-\-exclude\. Ignores any globally configured include and exclude paths to ensure that all objects are downloaded\.
+.
+.TP
+\fB\-\-prune\fR \fB\-p\fR
+Prune old and unreferenced objects after fetching, equivalent to running \fBgit lfs prune\fR afterwards\. See git\-lfs\-prune(1) for more details\.
+.
+.SH "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\.
+.
+.P
+In gitconfig, set \fBlfs\.fetchinclude\fR and \fBlfs\.fetchexclude\fR to comma\-separated lists of paths to include/exclude in the fetch\. Only paths which are matched by \fBfetchinclude\fR and not matched by \fBfetchexclude\fR will have objects fetched for them\.
+.
+.P
+Note that using the command\-line options \fB\-I\fR and \fB\-X\fR override the respective configuration settings\. Setting either option to an empty string clears the value\.
+.
+.SS "Examples:"
+.
+.IP "\(bu" 4
+\fBgit config lfs\.fetchinclude "textures,images/foo*"\fR
+.
+.IP
+This will only fetch objects referenced in paths in the textures folder, and files called foo* in the images folder
+.
+.IP "\(bu" 4
+\fBgit config lfs\.fetchinclude "*\.jpg,*\.png,*\.tga"\fR
+.
+.IP
+Only fetch JPG/PNG/TGA files, wherever they are in the repository
+.
+.IP "\(bu" 4
+\fBgit config lfs\.fetchexclude "media/reallybigfiles"\fR
+.
+.IP
+Don\'t fetch any LFS objects referenced in the folder media/reallybigfiles, but fetch everything else
+.
+.IP "\(bu" 4
+\fBgit config lfs\.fetchinclude "media"\fR
+.
+.br
+\fBgit config lfs\.fetchexclude "media/excessive"\fR
+.
+.IP
+Only fetch LFS objects in the \'media\' folder, but exclude those in one of its subfolders\.
+.
+.IP "" 0
+.
+.SH "DEFAULT REMOTE"
+Without arguments, fetch downloads from the default remote\. The default remote is the same as for \fBgit fetch\fR, i\.e\. based on the remote branch you\'re tracking first, or origin otherwise\.
+.
+.SH "DEFAULT REFS"
+If no refs are given as arguments, the currently checked out ref is used\. In addition, if enabled, recently changed refs and commits are also included\. See \fIRECENT CHANGES\fR for details\.
+.
+.SH "RECENT CHANGES"
+If the \fB\-\-recent\fR option is specified, or if the gitconfig option \fBlfs\.fetchrecentalways\fR is true, then after the current ref (or those in the arguments) is fetched, we also search for \'recent\' changes to fetch objects for, so that it\'s more convenient to checkout or diff those commits without incurring further downloads\.
+.
+.P
+What changes are considered \'recent\' is based on a number of gitconfig options:
+.
+.IP "\(bu" 4
+\fBlfs\.fetchrecentrefsdays\fR If non\-zero, includes branches which have commits within N days of the current date\. Only local refs are included unless lfs\.fetchrecentremoterefs is true\. The default is 7 days\.
+.
+.IP "\(bu" 4
+\fBlfs\.fetchrecentremoterefs\fR If true, fetches remote refs (for the remote you\'re fetching) as well as local refs in the recent window\. This is useful to fetch objects for remote branches you might want to check out later\. The default is true; if you set this to false, fetching for those branches will only occur when you either check them out (losing the advantage of fetch \-\-recent), or create a tracking local branch separately then fetch again\.
+.
+.IP "\(bu" 4
+\fBlfs\.fetchrecentcommitsdays\fR In addition to fetching at branches, also fetches changes made within N days of the latest commit on the branch\. This is useful if you\'re often reviewing recent changes\. The default is 0 (no previous changes)\.
+.
+.IP "\(bu" 4
+\fBlfs\.fetchrecentalways\fR Always operate as if \-\-recent was provided on the command line\.
+.
+.IP "" 0
+.
+.SH "EXAMPLES"
+.
+.IP "\(bu" 4
+Fetch the LFS objects for the current ref from default remote
+.
+.IP
+\fBgit lfs fetch\fR
+.
+.IP "\(bu" 4
+Fetch the LFS objects for the current ref AND recent changes from default remote
+.
+.IP
+\fBgit lfs fetch \-\-recent\fR
+.
+.IP "\(bu" 4
+Fetch the LFS objects for the current ref from a secondary remote \'upstream\'
+.
+.IP
+\fBgit lfs fetch upstream\fR
+.
+.IP "\(bu" 4
+Fetch all the LFS objects from the default remote that are referenced by any commit in the \fBmain\fR and \fBdevelop\fR branches
+.
+.IP
+\fBgit lfs fetch \-\-all origin main develop\fR
+.
+.IP "\(bu" 4
+Fetch the LFS objects for a branch from origin
+.
+.IP
+\fBgit lfs fetch origin mybranch\fR
+.
+.IP "\(bu" 4
+Fetch the LFS objects for 2 branches and a commit from origin
+.
+.IP
+\fBgit lfs fetch origin main mybranch e445b45c1c9c6282614f201b62778e4c0688b5c8\fR
+.
+.IP "" 0
+.
+.SH "SEE ALSO"
+git\-lfs\-checkout(1), git\-lfs\-pull(1), git\-lfs\-prune(1)\.
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-fetch.1.html

@@ -0,0 +1,228 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-fetch(1) - Download all Git LFS files for a given ref</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#OPTIONS">OPTIONS</a>
+    <a href="#INCLUDE-AND-EXCLUDE">INCLUDE AND EXCLUDE</a>
+    <a href="#DEFAULT-REMOTE">DEFAULT REMOTE</a>
+    <a href="#DEFAULT-REFS">DEFAULT REFS</a>
+    <a href="#RECENT-CHANGES">RECENT CHANGES</a>
+    <a href="#EXAMPLES">EXAMPLES</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-fetch(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-fetch(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-fetch</code> - <span class="man-whatis">Download all Git LFS files for a given ref</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs fetch</code> [options] [<var>remote</var> [<var>ref</var>...]]</p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Download Git LFS objects at the given refs from the specified remote. See
+<a href="#DEFAULT-REMOTE" title="DEFAULT REMOTE" data-bare-link="true">DEFAULT REMOTE</a> and <a href="#DEFAULT-REFS" title="DEFAULT REFS" data-bare-link="true">DEFAULT REFS</a> for what happens if you don't specify.</p>
+
+<p>This does not update the working copy.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<dl>
+<dt><code>-I</code> <var>paths</var> <code>--include=</code><var>paths</var></dt><dd><p>Specify lfs.fetchinclude just for this invocation; see <a href="#INCLUDE-AND-EXCLUDE" title="INCLUDE AND EXCLUDE" data-bare-link="true">INCLUDE AND EXCLUDE</a></p></dd>
+<dt><code>-X</code> <var>paths</var> <code>--exclude=</code><var>paths</var></dt><dd><p>Specify lfs.fetchexclude just for this invocation; see <a href="#INCLUDE-AND-EXCLUDE" title="INCLUDE AND EXCLUDE" data-bare-link="true">INCLUDE AND EXCLUDE</a></p></dd>
+<dt><code>--recent</code></dt><dd><p>Download objects referenced by recent branches &amp; commits in addition to those
+that would otherwise be downloaded. See <a href="#RECENT-CHANGES" title="RECENT CHANGES" data-bare-link="true">RECENT CHANGES</a></p></dd>
+<dt class="flush"><code>--all</code></dt><dd><p>Download all objects that are referenced by any commit reachable from the refs
+provided as arguments. If no refs are provided, then all refs are fetched.
+This is primarily for backup and migration purposes. Cannot be combined with
+--recent or --include/--exclude. Ignores any globally configured include and
+exclude paths to ensure that all objects are downloaded.</p></dd>
+<dt><code>--prune</code> <code>-p</code></dt><dd><p>Prune old and unreferenced objects after fetching, equivalent to running
+<code>git lfs prune</code> afterwards. See <span class="man-ref">git-lfs-prune<span class="s">(1)</span></span> for more details.</p></dd>
+</dl>
+
+
+<h2 id="INCLUDE-AND-EXCLUDE">INCLUDE AND EXCLUDE</h2>
+
+<p>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.</p>
+
+<p>In gitconfig, set <code>lfs.fetchinclude</code> and <code>lfs.fetchexclude</code> to comma-separated
+lists of paths to include/exclude in the fetch. Only paths which are matched by
+<code>fetchinclude</code> and not matched by <code>fetchexclude</code> will have objects fetched for
+them.</p>
+
+<p>Note that using the command-line options <code>-I</code> and <code>-X</code> override the respective
+configuration settings.  Setting either option to an empty string clears the
+value.</p>
+
+<h3 id="Examples-">Examples:</h3>
+
+<ul>
+<li><p><code>git config lfs.fetchinclude "textures,images/foo*"</code></p>
+
+<p>This will only fetch objects referenced in paths in the textures folder, and
+files called foo* in the images folder</p></li>
+<li><p><code>git config lfs.fetchinclude "*.jpg,*.png,*.tga"</code></p>
+
+<p>Only fetch JPG/PNG/TGA files, wherever they are in the repository</p></li>
+<li><p><code>git config lfs.fetchexclude "media/reallybigfiles"</code></p>
+
+<p>Don't fetch any LFS objects referenced in the folder media/reallybigfiles, but
+fetch everything else</p></li>
+<li><p><code>git config lfs.fetchinclude "media"</code><br />
+<code>git config lfs.fetchexclude "media/excessive"</code></p>
+
+<p>Only fetch LFS objects in the 'media' folder, but exclude those in one of its
+subfolders.</p></li>
+</ul>
+
+
+<h2 id="DEFAULT-REMOTE">DEFAULT REMOTE</h2>
+
+<p>Without arguments, fetch downloads from the default remote.  The default remote
+is the same as for <code>git fetch</code>, i.e. based on the remote branch you're tracking
+first, or origin otherwise.</p>
+
+<h2 id="DEFAULT-REFS">DEFAULT REFS</h2>
+
+<p>If no refs are given as arguments, the currently checked out ref is used. In
+addition, if enabled, recently changed refs and commits are also
+included. See <a href="#RECENT-CHANGES" title="RECENT CHANGES" data-bare-link="true">RECENT CHANGES</a> for details.</p>
+
+<h2 id="RECENT-CHANGES">RECENT CHANGES</h2>
+
+<p>If the <code>--recent</code> option is specified, or if the gitconfig option
+<code>lfs.fetchrecentalways</code> is true, then after the current ref (or those in the
+arguments) is fetched, we also search for 'recent' changes to fetch
+objects for, so that it's more convenient to checkout or diff those commits
+without incurring further downloads.</p>
+
+<p>What changes are considered 'recent' is based on a number of gitconfig options:</p>
+
+<ul>
+<li><p><code>lfs.fetchrecentrefsdays</code>
+If non-zero, includes branches which have commits within N days of the current
+date. Only local refs are included unless lfs.fetchrecentremoterefs is true.
+The default is 7 days.</p></li>
+<li><p><code>lfs.fetchrecentremoterefs</code>
+If true, fetches remote refs (for the remote you're fetching) as well as local
+refs in the recent window. This is useful to fetch objects for remote branches
+you might want to check out later. The default is true; if you set this to
+false, fetching for those branches will only occur when you either check them
+out (losing the advantage of fetch --recent), or create a tracking local
+branch separately then fetch again.</p></li>
+<li><p><code>lfs.fetchrecentcommitsdays</code>
+In addition to fetching at branches, also fetches changes made within N
+days of the latest commit on the branch. This is useful if you're often
+reviewing recent changes. The default is 0 (no previous changes).</p></li>
+<li><p><code>lfs.fetchrecentalways</code>
+Always operate as if --recent was provided on the command line.</p></li>
+</ul>
+
+
+<h2 id="EXAMPLES">EXAMPLES</h2>
+
+<ul>
+<li><p>Fetch the LFS objects for the current ref from default remote</p>
+
+<p><code>git lfs fetch</code></p></li>
+<li><p>Fetch the LFS objects for the current ref AND recent changes from default
+remote</p>
+
+<p><code>git lfs fetch --recent</code></p></li>
+<li><p>Fetch the LFS objects for the current ref from a secondary remote 'upstream'</p>
+
+<p><code>git lfs fetch upstream</code></p></li>
+<li><p>Fetch all the LFS objects from the default remote that are referenced by any
+commit in the <code>main</code> and <code>develop</code> branches</p>
+
+<p><code>git lfs fetch --all origin main develop</code></p></li>
+<li><p>Fetch the LFS objects for a branch from origin</p>
+
+<p><code>git lfs fetch origin mybranch</code></p></li>
+<li><p>Fetch the LFS objects for 2 branches and a commit from origin</p>
+
+<p><code>git lfs fetch origin main mybranch e445b45c1c9c6282614f201b62778e4c0688b5c8</code></p></li>
+</ul>
+
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><span class="man-ref">git-lfs-checkout<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-pull<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-prune<span class="s">(1)</span></span>.</p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-fetch(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-filter-process.1

@@ -0,0 +1,36 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-FILTER\-PROCESS" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-filter\-process\fR \- Git filter process that converts between pointer and actual content
+.
+.SH "SYNOPSIS"
+\fBgit lfs filter\-process\fR \fBgit lfs filter\-process \-\-skip\fR
+.
+.SH "DESCRIPTION"
+Implement the Git process filter API, exchanging handshake messages and then accepting and responding to requests to either clean or smudge a file\.
+.
+.P
+filter\-process is always run by Git\'s filter process, and is configured by the repository\'s Git attributes\.
+.
+.P
+The filter process uses Git\'s pkt\-line protocol to communicate, and is documented in detail in gitattributes(5)\.
+.
+.SH "OPTIONS"
+Without any options, filter\-process accepts and responds to requests normally\.
+.
+.TP
+\fB\-\-skip\fR
+Skip automatic downloading of objects on clone or pull\.
+.
+.TP
+\fBGIT_LFS_SKIP_SMUDGE\fR
+Disables the smudging process\. For more, see: git\-lfs\-config(5)\.
+.
+.SH "SEE ALSO"
+git\-lfs\-clean(1), git\-lfs\-install(1), git\-lfs\-smudge(1), gitattributes(5)\.
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-filter-process.1.html

@@ -0,0 +1,115 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-filter-process(1) - Git filter process that converts between pointer and actual content</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#OPTIONS">OPTIONS</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-filter-process(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-filter-process(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-filter-process</code> - <span class="man-whatis">Git filter process that converts between pointer and actual content</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs filter-process</code>
+<code>git lfs filter-process --skip</code></p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Implement the Git process filter API, exchanging handshake messages and then
+accepting and responding to requests to either clean or smudge a file.</p>
+
+<p>filter-process is always run by Git's filter process, and is configured by the
+repository's Git attributes.</p>
+
+<p>The filter process uses Git's pkt-line protocol to communicate, and is
+documented in detail in <span class="man-ref">gitattributes<span class="s">(5)</span></span>.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<p>Without any options, filter-process accepts and responds to requests normally.</p>
+
+<dl>
+<dt class="flush"><code>--skip</code></dt><dd><p>  Skip automatic downloading of objects on clone or pull.</p></dd>
+<dt><code>GIT_LFS_SKIP_SMUDGE</code></dt><dd><p>  Disables the smudging process. For more, see: <span class="man-ref">git-lfs-config<span class="s">(5)</span></span>.</p></dd>
+</dl>
+
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><span class="man-ref">git-lfs-clean<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-install<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-smudge<span class="s">(1)</span></span>, <span class="man-ref">gitattributes<span class="s">(5)</span></span>.</p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-filter-process(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-fsck.1

@@ -0,0 +1,38 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-FSCK" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-fsck\fR \- Check GIT LFS files for consistency
+.
+.SH "SYNOPSIS"
+\fBgit lfs fsck\fR [options] [revisions]
+.
+.SH "DESCRIPTION"
+Checks all GIT LFS files in the current HEAD for consistency\.
+.
+.P
+Corrupted files are moved to "\.git/lfs/bad"\.
+.
+.P
+The revisions may be specified as either a single committish, in which case only that commit is inspected; specified as a range of the form \fBA\.\.B\fR (and only this form), in which case that range is inspected; or omitted entirely, in which case HEAD (and, for \-\-objects, the index) is examined\.
+.
+.P
+The default is to perform all checks\.
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-\-objects\fR
+Check that each object in HEAD matches its expected hash and that each object exists on disk\.
+.
+.TP
+\fB\-\-pointers\fR
+Check that each pointer is canonical and that each file which should be stored as a Git LFS file is so stored\.
+.
+.SH "SEE ALSO"
+git\-lfs\-ls\-files(1), git\-lfs\-status(1)\.
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-fsck.1.html

@@ -0,0 +1,116 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-fsck(1) - Check GIT LFS files for consistency</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#OPTIONS">OPTIONS</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-fsck(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-fsck(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-fsck</code> - <span class="man-whatis">Check GIT LFS files for consistency</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs fsck</code> [options] [revisions]</p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Checks all GIT LFS files in the current HEAD for consistency.</p>
+
+<p>Corrupted files are moved to ".git/lfs/bad".</p>
+
+<p>The revisions may be specified as either a single committish, in which case only
+that commit is inspected; specified as a range of the form <code>A..B</code> (and only this
+form), in which case that range is inspected; or omitted entirely, in which case
+HEAD (and, for --objects, the index) is examined.</p>
+
+<p>The default is to perform all checks.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<dl>
+<dt><code>--objects</code></dt><dd>Check that each object in HEAD matches its expected hash and that each object
+exists on disk.</dd>
+<dt><code>--pointers</code></dt><dd>Check that each pointer is canonical and that each file which should be stored
+as a Git LFS file is so stored.</dd>
+</dl>
+
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><span class="man-ref">git-lfs-ls-files<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-status<span class="s">(1)</span></span>.</p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-fsck(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-install.1

@@ -0,0 +1,58 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-INSTALL" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-install\fR \- Install Git LFS configuration\.
+.
+.SH "SYNOPSIS"
+\fBgit lfs install\fR \fIoptions\fR
+.
+.SH "DESCRIPTION"
+Perform the following actions to ensure that Git LFS is setup properly:
+.
+.IP "\(bu" 4
+Set up the clean and smudge filters under the name "lfs" in the global Git config\.
+.
+.IP "\(bu" 4
+Install a pre\-push hook to run git\-lfs\-pre\-push(1) for the current repository, if run from inside one\. If "core\.hooksPath" is configured in any Git configuration (and supported, i\.e\., the installed Git version is at least 2\.9\.0), then the pre\-push hook will be installed to that directory instead\.
+.
+.IP "" 0
+.
+.SH "OPTIONS"
+Without any options, \fBgit lfs install\fR will only setup the "lfs" smudge and clean filters if they are not already set\.
+.
+.TP
+\fB\-\-force\fR
+Sets the "lfs" smudge and clean filters, overwriting existing values\.
+.
+.TP
+\fB\-\-local\fR
+Sets the "lfs" smudge and clean filters in the local repository\'s git config, instead of the global git config (~/\.gitconfig)\.
+.
+.TP
+\fB\-\-worktree\fR
+Sets the "lfs" smudge and clean filters in the current working tree\'s git config, instead of the global git config (~/\.gitconfig) or local repository\'s git config ($GIT_DIR/config)\. If multiple working trees are in use, the Git config extension \fBworktreeConfig\fR must be enabled to use this option\. If only one working tree is in use, \fB\-\-worktree\fR has the same effect as \fB\-\-local\fR\. This option is only available if the installed Git version is at least 2\.20\.0 and therefore supports the "worktreeConfig" extension\.
+.
+.TP
+\fB\-\-manual\fR
+Print instructions for manually updating your hooks to include git\-lfs functionality\. Use this option if \fBgit lfs install\fR fails because of existing hooks and you want to retain their functionality\.
+.
+.TP
+\fB\-\-system\fR
+Sets the "lfs" smudge and clean filters in the system git config, e\.g\. /etc/gitconfig instead of the global git config (~/\.gitconfig)\.
+.
+.TP
+\fB\-\-skip\-smudge\fR
+Skips automatic downloading of objects on clone or pull\. This requires a manual "git lfs pull" every time a new commit is checked out on your repository\.
+.
+.TP
+\fB\-\-skip\-repo\fR
+Skips setup of the local repo; use if you want to install the global lfs filters but not make changes to the current repo\.
+.
+.SH "SEE ALSO"
+git\-lfs\-uninstall(1), git\-worktree(1)\.
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-install.1.html

@@ -0,0 +1,138 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-install(1) - Install Git LFS configuration.</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#OPTIONS">OPTIONS</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-install(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-install(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-install</code> - <span class="man-whatis">Install Git LFS configuration.</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs install</code> <a href="#OPTIONS" title="OPTIONS" data-bare-link="true">options</a></p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Perform the following actions to ensure that Git LFS is setup properly:</p>
+
+<ul>
+<li>Set up the clean and smudge filters under the name "lfs" in the global Git
+config.</li>
+<li>Install a pre-push hook to run <span class="man-ref">git-lfs-pre-push<span class="s">(1)</span></span> for the current repository,
+if run from inside one. If "core.hooksPath" is configured in any Git
+configuration (and supported, i.e., the installed Git version is at least
+2.9.0), then the pre-push hook will be installed to that directory instead.</li>
+</ul>
+
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<p>Without any options, <code>git lfs install</code> will only setup the "lfs" smudge and clean
+filters if they are not already set.</p>
+
+<dl>
+<dt class="flush"><code>--force</code></dt><dd>  Sets the "lfs" smudge and clean filters, overwriting existing values.</dd>
+<dt class="flush"><code>--local</code></dt><dd>  Sets the "lfs" smudge and clean filters in the local repository's git
+  config, instead of the global git config (~/.gitconfig).</dd>
+<dt><code>--worktree</code></dt><dd>  Sets the "lfs" smudge and clean filters in the current working tree's
+  git config, instead of the global git config (~/.gitconfig) or local
+  repository's git config ($GIT_DIR/config).
+  If multiple working trees are in use, the Git config extension
+  <code>worktreeConfig</code> must be enabled to use this option.
+  If only one working tree is in use, <code>--worktree</code> has the same effect
+  as <code>--local</code>.
+  This option is only available if the installed Git version is at least
+  2.20.0 and therefore supports the "worktreeConfig" extension.</dd>
+<dt><code>--manual</code></dt><dd>  Print instructions for manually updating your hooks to include git-lfs
+  functionality. Use this option if <code>git lfs install</code> fails because of existing
+  hooks and you want to retain their functionality.</dd>
+<dt><code>--system</code></dt><dd>  Sets the "lfs" smudge and clean filters in the system git config, e.g. /etc/gitconfig
+  instead of the global git config (~/.gitconfig).</dd>
+<dt><code>--skip-smudge</code></dt><dd>  Skips automatic downloading of objects on clone or pull. This requires a
+  manual "git lfs pull" every time a new commit is checked out on your
+  repository.</dd>
+<dt><code>--skip-repo</code></dt><dd>  Skips setup of the local repo; use if you want to install the global lfs
+  filters but not make changes to the current repo.</dd>
+</dl>
+
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><span class="man-ref">git-lfs-uninstall<span class="s">(1)</span></span>, <span class="man-ref">git-worktree<span class="s">(1)</span></span>.</p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-install(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-lock.1

@@ -0,0 +1,32 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-LOCK" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-lock\fR \- Set a file as "locked" on the Git LFS server
+.
+.SH "SYNOPSIS"
+\fBgit lfs lock\fR \fIoptions\fR \fIpath\fR
+.
+.SH "DESCRIPTION"
+Sets the given file path as "locked" against the Git LFS server, with the intention of blocking attempts by other users to update the given path\. Locking a file requires the file to exist in the working copy\.
+.
+.P
+Once locked, LFS will verify that Git pushes do not modify files locked by other users\. See the description of the \fBlfs\.<url>\.locksverify\fR config key in git\-lfs\-config(5) for details\.
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-r\fR \fIname\fR \fB\-\-remote=\fR\fIname\fR
+Specify the Git LFS server to use\. Ignored if the \fBlfs\.url\fR config key is set\.
+.
+.TP
+\fB\-\-json\fR
+Writes lock info as JSON to STDOUT if the command exits successfully\. Intended for interoperation with external tools\. If the command returns with a non\-zero exit code, plain text messages will be sent to STDERR\.
+.
+.SH "SEE ALSO"
+git\-lfs\-unlock(1), git\-lfs\-locks(1)\.
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-lock.1.html

@@ -0,0 +1,113 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-lock(1) - Set a file as &quot;locked&quot; on the Git LFS server</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#OPTIONS">OPTIONS</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-lock(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-lock(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-lock</code> - <span class="man-whatis">Set a file as "locked" on the Git LFS server</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs lock</code> <a href="#OPTIONS" title="OPTIONS" data-bare-link="true">options</a> <var>path</var></p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Sets the given file path as "locked" against the Git LFS server, with the
+intention of blocking attempts by other users to update the given path. Locking
+a file requires the file to exist in the working copy.</p>
+
+<p>Once locked, LFS will verify that Git pushes do not modify files locked by
+other users. See the description of the <code>lfs.&lt;url>.locksverify</code> config key in
+<span class="man-ref">git-lfs-config<span class="s">(5)</span></span> for details.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<dl>
+<dt><code>-r</code> <var>name</var> <code>--remote=</code><var>name</var></dt><dd><p>Specify the Git LFS server to use. Ignored if the <code>lfs.url</code> config key is set.</p></dd>
+<dt class="flush"><code>--json</code></dt><dd><p>Writes lock info as JSON to STDOUT if the command exits successfully. Intended
+for interoperation with external tools. If the command returns with a non-zero
+exit code, plain text messages will be sent to STDERR.</p></dd>
+</dl>
+
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><span class="man-ref">git-lfs-unlock<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-locks<span class="s">(1)</span></span>.</p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-lock(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-locks.1

@@ -0,0 +1,53 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-LOCKS" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-locks\fR \- Lists currently locked files from the Git LFS server\.
+.
+.SH "SYNOPSIS"
+\fBgit lfs locks\fR \fIoptions\fR
+.
+.SH "DESCRIPTION"
+Lists current locks from the Git LFS server\.
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-r\fR \fIname\fR \fB\-\-remote=\fR\fIname\fR
+Specify the Git LFS server to use\. Ignored if the \fBlfs\.url\fR config key is set\.
+.
+.TP
+\fB\-i <id>\fR \fB\-\-id=<id>\fR
+Specifies a lock by its ID\. Returns a single result\.
+.
+.TP
+\fB\-p <path>\fR \fB\-\-path=<path>\fR
+Specifies a lock by its path\. Returns a single result\.
+.
+.TP
+\fB\-\-local\fR
+Lists only our own locks which are cached locally\. Skips a remote call\.
+.
+.TP
+\fB\-\-cached\fR
+Lists cached locks from the last remote call\. Contrary to \-\-local, this will include locks of other users as well\. This option is intended to display the last known locks in case you are offline\. There is no guarantee that locks on the server have not changed in the meanwhile\.
+.
+.TP
+\fB\-\-verify\fR
+Verifies the lock owner on the server and marks our own locks by \'O\'\. Own locks are actually held by us and corresponding files can be updated for the next push\. All other locks are held by someone else\. Contrary to \-\-local, this option will also detect locks which are held by us despite no local lock information being available (e\.g\. because the file had been locked from a different clone); it will also detect \'broken\' locks (e\.g\. if someone else has forcefully unlocked our files)\.
+.
+.TP
+\fB\-l <num>\fR \fB\-\-limit=<num>\fR
+Specifies number of results to return\.
+.
+.TP
+\fB\-\-json\fR
+Writes lock info as JSON to STDOUT if the command exits successfully\. Intended for interoperation with external tools\. If the command returns with a non\-zero exit code, plain text messages will be sent to STDERR\.
+.
+.SH "SEE ALSO"
+git\-lfs\-lock(1), git\-lfs\-unlock(1)\.
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-locks.1.html

@@ -0,0 +1,123 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-locks(1) - Lists currently locked files from the Git LFS server.</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#OPTIONS">OPTIONS</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-locks(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-locks(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-locks</code> - <span class="man-whatis">Lists currently locked files from the Git LFS server.</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs locks</code> <a href="#OPTIONS" title="OPTIONS" data-bare-link="true">options</a></p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Lists current locks from the Git LFS server.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<dl>
+<dt><code>-r</code> <var>name</var> <code>--remote=</code><var>name</var></dt><dd><p>Specify the Git LFS server to use. Ignored if the <code>lfs.url</code> config key is set.</p></dd>
+<dt><code>-i &lt;id></code> <code>--id=&lt;id></code></dt><dd><p>Specifies a lock by its ID. Returns a single result.</p></dd>
+<dt><code>-p &lt;path></code> <code>--path=&lt;path></code></dt><dd><p>Specifies a lock by its path. Returns a single result.</p></dd>
+<dt class="flush"><code>--local</code></dt><dd><p>Lists only our own locks which are cached locally. Skips a remote call.</p></dd>
+<dt><code>--cached</code></dt><dd><p>Lists cached locks from the last remote call. Contrary to --local, this will
+include locks of other users as well. This option is intended to display the
+last known locks in case you are offline. There is no guarantee that locks
+on the server have not changed in the meanwhile.</p></dd>
+<dt><code>--verify</code></dt><dd><p>Verifies the lock owner on the server and marks our own locks by 'O'.
+Own locks are actually held by us and corresponding files can be updated for
+the next push. All other locks are held by someone else.
+Contrary to --local, this option will also detect locks which are held by us
+despite no local lock information being available (e.g. because the file had
+been locked from a different clone);
+it will also detect 'broken' locks (e.g. if someone else has forcefully
+unlocked our files).</p></dd>
+<dt><code>-l &lt;num></code> <code>--limit=&lt;num></code></dt><dd><p>Specifies number of results to return.</p></dd>
+<dt class="flush"><code>--json</code></dt><dd><p>Writes lock info as JSON to STDOUT if the command exits successfully. Intended
+for interoperation with external tools. If the command returns with a non-zero
+exit code, plain text messages will be sent to STDERR.</p></dd>
+</dl>
+
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><span class="man-ref">git-lfs-lock<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-unlock<span class="s">(1)</span></span>.</p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-locks(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-logs.1

@@ -0,0 +1,44 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-LOGS" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-logs\fR \- Show errors from the git\-lfs command
+.
+.SH "SYNOPSIS"
+\fBgit lfs logs\fR
+.
+.br
+\fBgit lfs logs\fR \fIfile\fR
+.
+.br
+\fBgit lfs logs clear\fR
+.
+.br
+\fBgit lfs logs boomtown\fR
+.
+.br
+.
+.SH "DESCRIPTION"
+Display errors from the git\-lfs command\. Any time it crashes, the details are saved to "\.git/lfs/logs"\.
+.
+.SH "COMMANDS"
+.
+.TP
+\fBclear\fR
+Clears all of the existing logged errors\.
+.
+.TP
+\fBboomtown\fR
+Triggers a dummy exception\.
+.
+.SH "OPTIONS"
+Without any options, \fBgit lfs logs\fR simply shows the list of error logs\.
+.
+.TP
+\fIfile\fR
+Shows the specified error log\. Use "last" to show the most recent error\.
+.
+.SH "SEE ALSO"
+Part of the git\-lfs(1) suite\.

man/git-lfs-logs.1.html

@@ -0,0 +1,117 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-logs(1) - Show errors from the git-lfs command</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#COMMANDS">COMMANDS</a>
+    <a href="#OPTIONS">OPTIONS</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-logs(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-logs(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-logs</code> - <span class="man-whatis">Show errors from the git-lfs command</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs logs</code><br />
+<code>git lfs logs</code> <var>file</var><br />
+<code>git lfs logs clear</code><br />
+<code>git lfs logs boomtown</code><br /></p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Display errors from the git-lfs command.  Any time it crashes, the details are
+saved to ".git/lfs/logs".</p>
+
+<h2 id="COMMANDS">COMMANDS</h2>
+
+<dl>
+<dt class="flush"><code>clear</code></dt><dd><p>  Clears all of the existing logged errors.</p></dd>
+<dt><code>boomtown</code></dt><dd><p>  Triggers a dummy exception.</p></dd>
+</dl>
+
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<p>Without any options, <code>git lfs logs</code> simply shows the list of error logs.</p>
+
+<dl>
+<dt class="flush"><var>file</var></dt><dd>  Shows the specified error log.  Use "last" to show the most recent error.</dd>
+</dl>
+
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-logs(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-ls-files.1

@@ -0,0 +1,62 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-LS\-FILES" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-ls\-files\fR \- Show information about Git LFS files in the index and working tree
+.
+.SH "SYNOPSIS"
+\fBgit lfs ls\-files\fR [\fIref\fR]
+.
+.br
+\fBgit lfs ls\-files\fR \fIref\fR \fIref\fR
+.
+.SH "DESCRIPTION"
+Display paths of Git LFS files that are found in the tree at the given reference\. If no reference is given, scan the currently checked\-out branch\. If two references are given, the LFS files that are modified between the two references are shown; deletions are not listed\.
+.
+.P
+An asterisk (*) after the OID indicates a full object, a minus (\-) indicates an LFS pointer\.
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-l\fR \fB\-\-long\fR
+Show the entire 64 character OID, instead of just first 10\.
+.
+.TP
+\fB\-s\fR \fB\-\-size\fR
+Show the size of the LFS object between parenthesis at the end of a line\.
+.
+.TP
+\fB\-d\fR \fB\-\-debug\fR
+Show as much information as possible about a LFS file\. This is intended for manual inspection; the exact format may change at any time\.
+.
+.TP
+\fB\-a\fR \fB\-\-all\fR
+Inspects the full history of the repository, not the current HEAD (or other provided reference)\. This will include previous versions of LFS objects that are no longer found in the current tree\.
+.
+.TP
+\fB\-\-deleted\fR
+Shows the full history of the given reference, including objects that have been deleted\.
+.
+.TP
+\fB\-I\fR \fIpaths\fR \fB\-\-include=\fR\fIpaths\fR
+Include paths matching only these patterns; see [FETCH SETTINGS]\.
+.
+.TP
+\fB\-X\fR \fIpaths\fR \fB\-\-exclude=\fR\fIpaths\fR
+Exclude paths matching any of these patterns; see [FETCH SETTINGS]\.
+.
+.TP
+\fB\-n\fR \fB\-\-name\-only\fR
+Show only the lfs tracked file names\.
+.
+.SH "SEE ALSO"
+
+.
+.P
+git\-lfs\-status(1), git\-lfs\-config(5)\.
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-ls-files.1.html

@@ -0,0 +1,122 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-ls-files(1) - Show information about Git LFS files in the index and working tree</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#OPTIONS">OPTIONS</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-ls-files(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-ls-files(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-ls-files</code> - <span class="man-whatis">Show information about Git LFS files in the index and working tree</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs ls-files</code> [<var>ref</var>]<br />
+<code>git lfs ls-files</code> <var>ref</var> <var>ref</var></p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Display paths of Git LFS files that are found in the tree at the given
+reference.  If no reference is given, scan the currently checked-out branch.
+If two references are given, the LFS files that are modified between the two
+references are shown; deletions are not listed.</p>
+
+<p>An asterisk (*) after the OID indicates a full object, a minus (-) indicates an
+LFS pointer.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<dl>
+<dt><code>-l</code> <code>--long</code></dt><dd><p>Show the entire 64 character OID, instead of just first 10.</p></dd>
+<dt><code>-s</code> <code>--size</code></dt><dd><p>Show the size of the LFS object between parenthesis at the end of a line.</p></dd>
+<dt><code>-d</code> <code>--debug</code></dt><dd><p>Show as much information as possible about a LFS file. This is intended
+for manual inspection; the exact format may change at any time.</p></dd>
+<dt><code>-a</code> <code>--all</code></dt><dd><p>Inspects the full history of the repository, not the current HEAD (or other
+provided reference). This will include previous versions of LFS objects that
+are no longer found in the current tree.</p></dd>
+<dt><code>--deleted</code></dt><dd><p>Shows the full history of the given reference, including objects that have
+been deleted.</p></dd>
+<dt><code>-I</code> <var>paths</var> <code>--include=</code><var>paths</var></dt><dd><p>Include paths matching only these patterns; see [FETCH SETTINGS].</p></dd>
+<dt><code>-X</code> <var>paths</var> <code>--exclude=</code><var>paths</var></dt><dd><p>Exclude paths matching any of these patterns; see [FETCH SETTINGS].</p></dd>
+<dt><code>-n</code> <code>--name-only</code></dt><dd><p>Show only the lfs tracked file names.</p>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2></dd>
+</dl>
+
+
+<p><span class="man-ref">git-lfs-status<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-config<span class="s">(5)</span></span>.</p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-ls-files(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-migrate.1

@@ -0,0 +1,405 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-MIGRATE" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-migrate\fR \- Migrate history to or from Git LFS
+.
+.SH "SYNOPSIS"
+\fBgit lfs migrate\fR \fImode\fR [options] [\-\-] [branch \.\.\.]
+.
+.SH "DESCRIPTION"
+Convert files in a Git repository to or from Git LFS pointers, or summarize Git file sizes by file type\. The \fBimport\fR mode converts Git files (i\.e\., blobs) to Git LFS, while the \fBexport\fR mode does the reverse, and the \fBinfo\fR mode provides an informational summary which may be useful in deciding which files to import or export\.
+.
+.P
+In all modes, by default \fBgit lfs migrate\fR operates only on the currently checked\-out branch, and only on files (of any size and type) added in commits which do not exist on any remote\. Multiple options are available to override these defaults\.
+.
+.P
+When converting files to or from Git LFS, the \fBgit lfs migrate\fR command will only make changes to your local repository and working copy, never any remotes\. This is intentional as the \fBimport\fR and \fBexport\fR modes are generally "destructive" in the sense that they rewrite your Git history, changing commits and generating new commit SHAs\. (The exception is the "no\-rewrite" \fBimport\fR sub\-mode; see [IMPORT (NO REWRITE)] for details\.)
+.
+.P
+You should therefore always first commit or stash any uncommitted work before using the \fBimport\fR or \fBexport\fR modes, and then validate the result of the migration before pushing the changes to your remotes, for instance by running the \fBinfo\fR mode and by examining your rewritten commit history\.
+.
+.P
+Once you are satisfied with the changes, you will need to force\-push the new Git history of any rewritten branches to all your remotes\. This is a step which should be taken with care, since you will be altering the Git history on your remotes\.
+.
+.P
+To examine or modify files in branches other than the currently checked\-out one, branch refs may be specified directly, or provided in one or more \fB\-\-include\-ref\fR options\. They may also be excluded by prefixing them with \fB^\fR or providing them in \fB\-\-exclude\-ref\fR options\. Use the \fB\-\-everything\fR option to specify that all refs should be examined, including all remote refs\. See [INCLUDE AND EXCLUDE (REFS)] for details\.
+.
+.P
+For the \fBinfo\fR and \fBimport\fR modes, all file types are considered by default; while useful in the \fBinfo\fR mode, this is often not desirable when importing, so either filename patterns (pathspecs) or the \fB\-\-fixup\fR option should normally be specified in that case\. (At least one include pathspec is required for the \fBexport\fR mode\.) Pathspecs may be defined using the \fB\-\-include\fR and \fB\-\-exclude\fR options (\fB\-I\fR and \fB\-X\fR for short), as described in \fIINCLUDE AND EXCLUDE\fR\.
+.
+.P
+As typical Git LFS usage depends on tracking specific file types using filename patterns defined in \fB\.gitattributes\fR files, the \fBgit lfs migrate\fR command will examine, create, and modify \fB\.gitattributes\fR files as necessary\.
+.
+.P
+The \fBimport\fR mode (see \fIIMPORT\fR) will convert Git objects of the file types specified (e\.g\., with \fB\-\-include\fR) to Git LFS pointers, and will add entries for those file types to \fB\.gitattributes\fR files, creating those files if they do not exist\. The result should be as if \fBgit lfs track\fR commands had been run at the points in your Git history corresponding to where each type of converted file first appears\. The exception is if the \fB\-\-fixup\fR option is given, in which case the \fBimport\fR mode will only examine any existing \fB\.gitattributes\fR files and then convert Git objects which should be tracked by Git LFS but are not yet\.
+.
+.P
+The \fBexport\fR mode (see \fIEXPORT\fR) works as the reverse operation to the \fBimport\fR mode, converting any Git LFS pointers that match the file types specified with \fB\-\-include\fR, which must be given at least once\. Note that \fB\.gitattributes\fR entries will not be removed, nor will the files; instead, the \fBexport\fR mode inserts "do not track" entries similar to those created by the \fBgit lfs untrack\fR command\. The \fB\-\-remote\fR option is available in the \fBexport\fR mode to specify the remote from which Git LFS objects should be fetched if they do not exist in the local Git LFS object cache; if not provided, \fBorigin\fR is used by default\.
+.
+.P
+The \fBinfo\fR mode (see \fIINFO\fR) summarizes by file type (i\.e\., by filename extension) the total number and size of files in a repository\. Note that like the other two modes, by default the \fBinfo\fR mode operates only on the currently checked\-out branch and only on commits which do not exist on any remote, so to get a summary of the entire repository across all branches, use the \fB\-\-everything\fR option\. If objects have already been converted to Git LFS pointers, then by default the size of the referenced objects is totaled and reported separately\. You may also choose to ignore them by using \fB\-\-pointers=ignore\fR or to treat the pointers as files by using \fB\-\-pointers=no\-follow\fR\. (The latter option is akin to how existing Git LFS pointers were handled by the \fBinfo\fR mode in prior versions of Git LFS)\.
+.
+.P
+When using the \fB\-\-everything\fR option, take note that it means all refs (local and remote) will be considered, but not necessarily all file types\. The \fBimport\fR and \fBinfo\fR modes consider all file types by default, although the \fB\-\-include\fR and \fB\-\-exclude\fR options constrain this behavior\. Also note that after importing across all branches with the \fB\-\-everything\fR option (and then checking to ensure the results are satisfactory!) it may be convenient to update multiple branches on your remotes by using the \fB\-\-all\fR option to \fBgit push\fR\.
+.
+.P
+Unless the \fB\-\-skip\-fetch\fR option is given, \fBgit lfs migrate\fR always begins by fetching updated lists of refs from all the remotes returned by \fBgit remote\fR, but as noted above, after making changes to your local Git history while converting objects, it will never automatically push those changes to your remotes\.
+.
+.SH "MODES"
+.
+.IP "\(bu" 4
+\fBinfo\fR Show information about repository size\. See \fIINFO\fR\.
+.
+.IP "\(bu" 4
+\fBimport\fR Convert Git objects to Git LFS pointers\. See \fIIMPORT\fR and [IMPORT (NO REWRITE)]\.
+.
+.IP "\(bu" 4
+\fBexport\fR Convert Git LFS pointers to Git objects\. See \fIEXPORT\fR\.
+.
+.IP "" 0
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-I\fR \fIpaths\fR \fB\-\-include=\fR\fIpaths\fR
+See \fIINCLUDE AND EXCLUDE\fR\.
+.
+.TP
+\fB\-X\fR \fIpaths\fR \fB\-\-exclude=\fR\fIpaths\fR
+See \fIINCLUDE AND EXCLUDE\fR\.
+.
+.TP
+\fB\-\-include\-ref\fR=\fIrefname\fR
+See [INCLUDE AND EXCLUDE (REFS)]\.
+.
+.TP
+\fB\-\-exclude\-ref\fR=\fIrefname\fR
+See [INCLUDE AND EXCLUDE (REFS)]\.
+.
+.TP
+\fB\-\-skip\-fetch\fR
+Assumes that the known set of remote references is complete, and should not be refreshed when determining the set of "un\-pushed" commits to migrate\. Has no effect when combined with \fB\-\-include\-ref\fR or \fB\-\-exclude\-ref\fR\.
+.
+.TP
+\fB\-\-everything\fR
+See [INCLUDE AND EXCLUDE (REFS)]\.
+.
+.IP
+Note: Git refs are "case\-sensitive" on all platforms in "packed from" (see \fBgit\-pack\-refs(1)\fR)\. On "case\-insensitive" file systems, e\.g\. NTFS on Windows or default APFS on macOS, \fBgit\-lfs\-migrate(1)\fR would only migrate the first ref if two or more refs are equal except for upper/lower case letters\.
+.
+.TP
+\fB\-\-yes\fR
+Assume a yes answer to any prompts, permitting noninteractive use\. Currently, the only such prompt is the one asking whether to overwrite (destroy) any working copy changes\. Thus, specifying this option may cause data loss if you are not careful\.
+.
+.TP
+[branch \.\.\.]
+Migrate only the set of branches listed\. If not given, \fBgit\-lfs\-migrate(1)\fR will migrate the currently checked out branch\.
+.
+.IP
+References beginning with \fB^\fR will be excluded, whereas branches that do not begin with \fB^\fR will be included\.
+.
+.IP
+If any of \fB\-\-include\-ref\fR or \fB\-\-exclude\-ref\fR are given, the checked out branch will not be appended, but branches given explicitly will be appended\.
+.
+.SS "INFO"
+The \fBinfo\fR mode summarizes the sizes of file objects present in the Git history\. It supports all the core \fBmigrate\fR options and these additional ones:
+.
+.IP "\(bu" 4
+\fB\-\-above=<size>\fR Only count files whose individual filesize is above the given size\. \fBsize\fR may be specified as a number of bytes, or a number followed by a storage unit, e\.g\., "1b", "20 MB", "3 TiB", etc\.
+.
+.IP
+If a set of files sharing a common extension has no files in that set whose individual size is above the given \fB\-\-above\fR no files no entry for that set will be shown\.
+.
+.IP "\(bu" 4
+\fB\-\-top=<n>\fR Only display the top \fBn\fR entries, ordered by how many total files match the given pathspec\. The default is to show only the top 5 entries\. When existing Git LFS objects are found, an extra, separate "LFS Objects" line is output in addition to the top \fBn\fR entries, unless the \fB\-\-pointers\fR option is used to change this behavior\.
+.
+.IP "\(bu" 4
+\fB\-\-unit=<unit>\fR Format the number of bytes in each entry as a quantity of the storage unit provided\. Valid units include:
+.
+.IP "" 4
+.
+.nf
+
+* b, kib, mib, gib, tib, pib \- for IEC storage units
+* b, kb, mb, gb, tb, pb \- for SI storage units
+.
+.fi
+.
+.IP "" 0
+.
+.IP
+If a \fB\-\-unit\fR is not specified, the largest unit that can fit the number of counted bytes as a whole number quantity is chosen\.
+.
+.IP "\(bu" 4
+\fB\-\-pointers=[follow|no\-follow|ignore]\fR Treat existing Git LFS pointers in the history according to one of three alternatives\. In the default \fBfollow\fR case, if any pointers are found, an additional separate "LFS Objects" line item is output which summarizes the total number and size of the Git LFS objects referenced by pointers\. In the \fBignore\fR case, any pointers are simply ignored, while the \fBno\-follow\fR case replicates the behavior of the \fBinfo\fR mode in older Git LFS versions and treats any pointers it finds as if they were regular files, so the output totals only include the contents of the pointers, not the contents of the objects to which they refer\.
+.
+.IP "\(bu" 4
+\fB\-\-fixup\fR Infer \fB\-\-include\fR and \fB\-\-exclude\fR filters on a per\-commit basis based on the \.gitattributes files in a repository\. In practice, this option counts any filepaths which should be tracked by Git LFS according to the repository\'s \.gitattributes file(s), but aren\'t already pointers\. The \.gitattributes files are not reported, in contrast to the normal output of the \fBinfo\fR mode\. This option is incompatible with explicitly given \fB\-\-include\fR, \fB\-\-exclude\fR filters and with any \fB\-\-pointers\fR setting other than \fBignore\fR, hence \fB\-\-fixup\fR implies \fB\-\-pointers=ignore\fR if it is not explicitly set\.
+.
+.IP "" 0
+.
+.P
+The format of the output shows the filename pattern, the total size of the file objects (excluding those below the \fB\-\-above\fR threshold, if one was defined), and the ratio of the number of files above the threshold to the total number of files; this ratio is also shown as a percentage\. For example:
+.
+.IP "" 4
+.
+.nf
+
+*\.gif               93 MB   9480/10504 files(s)  90%
+*\.png               14 MB    1732/1877 files(s)  92%
+.
+.fi
+.
+.IP "" 0
+.
+.P
+By default only the top five entries are shown, but \fB\-\-top\fR allows for more or fewer to be output as desired\.
+.
+.SS "IMPORT"
+The \fBimport\fR mode migrates objects present in the Git history to pointer files tracked and stored with Git LFS\. It supports all the core \fBmigrate\fR options and these additional ones:
+.
+.IP "\(bu" 4
+\fB\-\-verbose\fR Print the commit oid and filename of migrated files to STDOUT\.
+.
+.IP "\(bu" 4
+\fB\-\-above=<size>\fR Only migrate files whose individual filesize is above the given size\. \fBsize\fR may be specified as a number of bytes, or a number followed by a storage unit, e\.g\., "1b", "20 MB", "3 TiB", etc\.
+.
+.IP "\(bu" 4
+\fB\-\-object\-map=<path>\fR Write to \fBpath\fR a file with the mapping of each rewritten commits\. The file format is CSV with this pattern: \fBOLD\-SHA\fR,\fBNEW\-SHA\fR
+.
+.IP "\(bu" 4
+\fB\-\-no\-rewrite\fR Migrate objects to Git LFS in a new commit without rewriting Git history\. Please note that when this option is used, the \fBmigrate import\fR command will expect a different argument list, specialized options will become available, and the core \fBmigrate\fR options will be ignored\. See [IMPORT (NO REWRITE)]\.
+.
+.IP "\(bu" 4
+\fB\-\-fixup\fR Infer \fB\-\-include\fR and \fB\-\-exclude\fR filters on a per\-commit basis based on the \fB\.gitattributes\fR files in a repository\. In practice, this option imports any filepaths which should be tracked by Git LFS according to the repository\'s \fB\.gitattributes\fR file(s), but aren\'t already pointers\. This option is incompatible with explicitly given \fB\-\-include\fR, \fB\-\-exclude\fR filters\.
+.
+.IP "" 0
+.
+.P
+If \fB\-\-no\-rewrite\fR is not provided and \fB\-\-include\fR or \fB\-\-exclude\fR (\fB\-I\fR, \fB\-X\fR, respectively) are given, the \fB\.gitattributes\fR will be modified to include any new filepath patterns as given by those flags\.
+.
+.P
+If \fB\-\-no\-rewrite\fR is not provided and neither of those flags are given, the gitattributes will be incrementally modified to include new filepath extensions as they are rewritten in history\.
+.
+.SS "IMPORT (NO REWRITE)"
+The \fBimport\fR mode has a special sub\-mode enabled by the \fB\-\-no\-rewrite\fR flag\. This sub\-mode will migrate objects to pointers as in the base \fBimport\fR mode, but will do so in a new commit without rewriting Git history\. When using this sub\-mode, the base \fBmigrate\fR options, such as \fB\-\-include\-ref\fR, will be ignored, as will those for the base \fBimport\fR mode\. The \fBmigrate\fR command will also take a different argument list\. As a result of these changes, \fB\-\-no\-rewrite\fR will only operate on the current branch \- any other interested branches must have the generated commit merged in\.
+.
+.P
+The \fB\-\-no\-rewrite\fR sub\-mode supports the following options and arguments:
+.
+.IP "\(bu" 4
+\fB\-m <message> \-\-message=<message>\fR Specifies a commit message for the newly created commit\.
+.
+.IP "\(bu" 4
+[file \.\.\.] The list of files to import\. These files must be tracked by patterns specified in the gitattributes\.
+.
+.IP "" 0
+.
+.P
+If \fB\-\-message\fR is given, the new commit will be created with the provided message\. If no message is given, a commit message will be generated based on the file arguments\.
+.
+.SS "EXPORT"
+The \fBexport\fR mode migrates Git LFS pointer files present in the Git history out of Git LFS, converting them into their corresponding object files\. It supports all the core \fBmigrate\fR options and these additional ones:
+.
+.IP "\(bu" 4
+\fB\-\-verbose\fR Print the commit oid and filename of migrated files to STDOUT\.
+.
+.IP "\(bu" 4
+\fB\-\-object\-map=<path>\fR Write to \fBpath\fR a file with the mapping of each rewritten commit\. The file format is CSV with this pattern: \fBOLD\-SHA\fR,\fBNEW\-SHA\fR
+.
+.IP "\(bu" 4
+\fB\-\-remote=<git\-remote>\fR Download LFS objects from the provided \fBgit\-remote\fR during the export\. If not provided, defaults to \fBorigin\fR\.
+.
+.IP "" 0
+.
+.P
+The \fBexport\fR mode requires at minimum a pattern provided with the \fB\-\-include\fR argument to specify which files to export\. Files matching the \fB\-\-include\fR patterns will be removed from Git LFS, while files matching the \fB\-\-exclude\fR patterns will retain their Git LFS status\. The export command will modify the \fB\.gitattributes\fR to set/unset any filepath patterns as given by those flags\.
+.
+.SH "INCLUDE AND EXCLUDE"
+You can specify that \fBgit lfs migrate\fR should only convert files whose pathspec matches the \fB\-\-include\fR glob patterns and does not match the \fB\-\-exclude\fR glob patterns, either to reduce total migration time or to only migrate part of your repo\. Multiple patterns may be given using commas as delimiters\.
+.
+.P
+Pattern matching is done so as to be functionally equivalent to the pattern matching format of \fB\.gitattributes\fR\. In addition to simple file extension matches (e\.g\., \fB*\.gif\fR) patterns may also specify directory paths, in which case the \fBpath/**\fR format may be used to match recursively\.
+.
+.SH "INCLUDE AND EXCLUDE (REFS)"
+You can specify that \fBgit lfs migrate\fR should only convert files added in commits reachable from certain references, namely those defined using one or more \fB\-\-include\-ref\fR options, and should ignore files in commits reachable from references defined in \fB\-\-exclude\-ref\fR options\.
+.
+.IP "" 4
+.
+.nf
+
+        D\-\-\-E\-\-\-F
+       /         \e
+  A\-\-\-B\-\-\-\-\-\-C    refs/heads/my\-feature
+   \e          \e
+    \e          refs/heads/main
+     \e
+      refs/remotes/origin/main
+.
+.fi
+.
+.IP "" 0
+.
+.P
+In the above configuration, the following commits are reachable by each ref:
+.
+.IP "" 4
+.
+.nf
+
+refs/heads/main:           C, B, A
+refs/heads/my\-feature:     F, E, D, B, A
+refs/remote/origin/main:   A
+.
+.fi
+.
+.IP "" 0
+.
+.P
+The following \fBgit lfs migrate\fR options would, therefore, include commits F, E, D, C, and B, but exclude commit A:
+.
+.IP "" 4
+.
+.nf
+
+  \-\-include\-ref=refs/heads/my\-feature
+  \-\-include\-ref=refs/heads/main
+  \-\-exclude\-ref=refs/remotes/origin/main
+.
+.fi
+.
+.IP "" 0
+.
+.P
+The presence of flag \fB\-\-everything\fR indicates that all local and remote references should be migrated\.
+.
+.SH "EXAMPLES"
+.
+.SS "Migrate unpushed commits"
+A common use case for the migrate command is to convert large Git objects to LFS before pushing your commits\. By default, it only scans commits that don\'t exist on any remote, so long as the repository is non\-bare\.
+.
+.P
+First, run \fBgit lfs migrate info\fR to list the file types taking up the most space in your repository:
+.
+.IP "" 4
+.
+.nf
+
+$ git lfs migrate info
+migrate: Fetching remote refs: \.\.\., done
+migrate: Sorting commits: \.\.\., done
+migrate: Examining commits: 100% (1/1), done
+*\.mp3   284 MB    1/1 files(s)  100%
+*\.pdf   42 MB     8/8 files(s)  100%
+*\.psd   9\.8 MB  15/15 files(s)  100%
+*\.ipynb 6\.9 MB    6/6 files(s)  100%
+*\.csv   5\.8 MB    2/2 files(s)  100%
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Now, you can run \fBgit lfs migrate import\fR to convert some file types to LFS:
+.
+.IP "" 4
+.
+.nf
+
+$ git lfs migrate import \-\-include="*\.mp3,*\.psd"
+migrate: Fetching remote refs: \.\.\., done
+migrate: Sorting commits: \.\.\., done
+migrate: Rewriting commits: 100% (1/1), done
+  main  d2b959babd099fe70da1c1512e2475e8a24de163 \-> 136e706bf1ae79643915c134e17a6c933fd53c61
+migrate: Updating refs: \.\.\., done
+.
+.fi
+.
+.IP "" 0
+.
+.P
+If after conversion you find that some files in your working directory have been replaced with Git LFS pointers, this is normal, and the working copies of these files can be repopulated with their full expected contents by using \fBgit lfs checkout\fR\.
+.
+.SS "Migrate local history"
+You can also migrate the entire history of your repository:
+.
+.IP "" 4
+.
+.nf
+
+# Check for large files and existing Git LFS objects in your local main branch
+$ git lfs migrate info \-\-include\-ref=main
+
+# Check for large files and existing Git LFS objects in every branch
+$ git lfs migrate info \-\-everything
+
+# Check for large files in every branch, ignoring any existing Git LFS objects,
+# and listing the top 100 or fewer results
+$ git lfs migrate info \-\-everything \-\-pointers=ignore \-\-top=100
+.
+.fi
+.
+.IP "" 0
+.
+.P
+The same flags will work in \fBimport\fR mode:
+.
+.IP "" 4
+.
+.nf
+
+# Convert all zip files in your main branch
+$ git lfs migrate import \-\-include\-ref=main \-\-include="*\.zip"
+
+# Convert all zip files in every local branch
+$ git lfs migrate import \-\-everything \-\-include="*\.zip"
+
+# Convert all files over 100K in every local branch
+$ git lfs migrate import \-\-everything \-\-above=100Kb
+.
+.fi
+.
+.IP "" 0
+.
+.P
+Note: This will require a force\-push to any existing Git remotes\. Using the \fB\-\-all\fR option when force\-pushing may be convenient if many refs were updated, e\.g\., after importing to Git LFS with the \fB\-\-everything\fR option\.
+.
+.SS "Migrate without rewriting local history"
+You can also migrate files without modifying the existing history of your repository\. Note that in the examples below, files in subdirectories are not included because they are not explicitly specified\.
+.
+.P
+Without a specified commit message:
+.
+.IP "" 4
+.
+.nf
+
+$ git lfs migrate import \-\-no\-rewrite test\.zip *\.mp3 *\.psd
+.
+.fi
+.
+.IP "" 0
+.
+.P
+With a specified commit message:
+.
+.IP "" 4
+.
+.nf
+
+$ git lfs migrate import \-\-no\-rewrite \e
+  \-m "Import test\.zip, \.mp3, \.psd files in root of repo" \e
+  test\.zip *\.mp3 *\.psd
+.
+.fi
+.
+.IP "" 0
+.
+.SH "SEE ALSO"
+git\-lfs\-checkout(1), git\-lfs\-track(1), git\-lfs\-untrack(1), gitattributes(5)\.
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-migrate.1.html

@@ -0,0 +1,523 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-migrate(1) - Migrate history to or from Git LFS</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#MODES">MODES</a>
+    <a href="#OPTIONS">OPTIONS</a>
+    <a href="#INCLUDE-AND-EXCLUDE">INCLUDE AND EXCLUDE</a>
+    <a href="#INCLUDE-AND-EXCLUDE-REFS-">INCLUDE AND EXCLUDE (REFS)</a>
+    <a href="#EXAMPLES">EXAMPLES</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-migrate(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-migrate(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-migrate</code> - <span class="man-whatis">Migrate history to or from Git LFS</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs migrate</code> <var>mode</var> [options] [--] [branch ...]</p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Convert files in a Git repository to or from Git LFS pointers, or
+summarize Git file sizes by file type.  The <code>import</code> mode converts Git
+files (i.e., blobs) to Git LFS, while the <code>export</code> mode does the reverse,
+and the <code>info</code> mode provides an informational summary which may be useful
+in deciding which files to import or export.</p>
+
+<p>In all modes, by default <code>git lfs migrate</code> operates only on the currently
+checked-out branch, and only on files (of any size and type) added in
+commits which do not exist on any remote.  Multiple options are available
+to override these defaults.</p>
+
+<p>When converting files to or from Git LFS, the <code>git lfs migrate</code> command will
+only make changes to your local repository and working copy, never any
+remotes.  This is intentional as the <code>import</code> and <code>export</code> modes are
+generally "destructive" in the sense that they rewrite your Git history,
+changing commits and generating new commit SHAs.  (The exception is the
+"no-rewrite" <code>import</code> sub-mode; see [IMPORT (NO REWRITE)] for details.)</p>
+
+<p>You should therefore always first commit or stash any uncommitted work
+before using the <code>import</code> or <code>export</code> modes, and then validate the result of
+the migration before pushing the changes to your remotes, for instance by
+running the <code>info</code> mode and by examining your rewritten commit history.</p>
+
+<p>Once you are satisfied with the changes, you will need to force-push the
+new Git history of any rewritten branches to all your remotes.  This is
+a step which should be taken with care, since you will be altering the
+Git history on your remotes.</p>
+
+<p>To examine or modify files in branches other than the currently checked-out
+one, branch refs may be specified directly, or provided in one or more
+<code>--include-ref</code> options.  They may also be excluded by prefixing them
+with <code>^</code> or providing them in <code>--exclude-ref</code> options.  Use the <code>--everything</code>
+option to specify that all refs should be examined, including all remote refs.
+See [INCLUDE AND EXCLUDE (REFS)] for details.</p>
+
+<p>For the <code>info</code> and <code>import</code> modes, all file types are considered by default;
+while useful in the <code>info</code> mode, this is often not desirable when importing,
+so either filename patterns (pathspecs) or the <code>--fixup</code> option should
+normally be specified in that case.  (At least one include pathspec is
+required for the <code>export</code> mode.)  Pathspecs may be defined using the
+<code>--include</code> and <code>--exclude</code> options (<code>-I</code> and <code>-X</code> for short), as described
+in <a href="#INCLUDE-AND-EXCLUDE" title="INCLUDE AND EXCLUDE" data-bare-link="true">INCLUDE AND EXCLUDE</a>.</p>
+
+<p>As typical Git LFS usage depends on tracking specific file types using
+filename patterns defined in <code>.gitattributes</code> files, the <code>git lfs migrate</code>
+command will examine, create, and modify <code>.gitattributes</code> files as
+necessary.</p>
+
+<p>The <code>import</code> mode (see <a href="#IMPORT" title="IMPORT" data-bare-link="true">IMPORT</a>) will convert Git objects of the file types
+specified (e.g., with <code>--include</code>) to Git LFS pointers, and will add entries
+for those file types to <code>.gitattributes</code> files, creating those files if they
+do not exist.  The result should be as if <code>git lfs track</code> commands had been
+run at the points in your Git history corresponding to where each type of
+converted file first appears.  The exception is if the <code>--fixup</code> option is
+given, in which case the <code>import</code> mode will only examine any existing
+<code>.gitattributes</code> files and then convert Git objects which should be tracked
+by Git LFS but are not yet.</p>
+
+<p>The <code>export</code> mode (see <a href="#EXPORT" title="EXPORT" data-bare-link="true">EXPORT</a>) works as the reverse operation to the
+<code>import</code> mode, converting any Git LFS pointers that match the file types
+specified with <code>--include</code>, which must be given at least once.  Note that
+<code>.gitattributes</code> entries will not be removed, nor will the files; instead,
+the <code>export</code> mode inserts "do not track" entries similar to those created
+by the <code>git lfs untrack</code> command.  The <code>--remote</code> option is available in
+the <code>export</code>  mode to specify the remote from which Git LFS objects should
+be fetched if they do not exist in the local Git LFS object cache; if not
+provided, <code>origin</code> is used by default.</p>
+
+<p>The <code>info</code> mode (see <a href="#INFO" title="INFO" data-bare-link="true">INFO</a>) summarizes by file type (i.e., by filename
+extension) the total number and size of files in a repository.  Note that
+like the other two modes, by default the <code>info</code> mode operates only on
+the currently checked-out branch and only on commits which do not exist on
+any remote, so to get a summary of the entire repository across all branches,
+use the <code>--everything</code> option.  If objects have already been converted to
+Git LFS pointers, then by default the size of the referenced objects is
+totaled and reported separately.  You may also choose to ignore them by
+using <code>--pointers=ignore</code> or to treat the pointers as files by using
+<code>--pointers=no-follow</code>.  (The latter option is akin to how existing Git LFS
+pointers were handled by the <code>info</code> mode in prior versions of Git LFS).</p>
+
+<p>When using the <code>--everything</code> option, take note that it means all refs
+(local and remote) will be considered, but not necessarily all file types.
+The <code>import</code> and <code>info</code> modes consider all file types by default, although
+the <code>--include</code> and <code>--exclude</code> options constrain this behavior.  Also
+note that after importing across all branches with the <code>--everything</code> option
+(and then checking to ensure the results are satisfactory!) it may be
+convenient to update multiple branches on your remotes by using the <code>--all</code>
+option to <code>git push</code>.</p>
+
+<p>Unless the <code>--skip-fetch</code> option is given, <code>git lfs migrate</code> always begins by
+fetching updated lists of refs from all the remotes returned by <code>git remote</code>,
+but as noted above, after making changes to your local Git history while
+converting objects, it will never automatically push those changes to your
+remotes.</p>
+
+<h2 id="MODES">MODES</h2>
+
+<ul>
+<li><p><code>info</code>
+  Show information about repository size.  See <a href="#INFO" title="INFO" data-bare-link="true">INFO</a>.</p></li>
+<li><p><code>import</code>
+  Convert Git objects to Git LFS pointers.  See <a href="#IMPORT" title="IMPORT" data-bare-link="true">IMPORT</a> and [IMPORT (NO REWRITE)].</p></li>
+<li><p><code>export</code>
+  Convert Git LFS pointers to Git objects.  See <a href="#EXPORT" title="EXPORT" data-bare-link="true">EXPORT</a>.</p></li>
+</ul>
+
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<dl>
+<dt><code>-I</code> <var>paths</var> <code>--include=</code><var>paths</var></dt><dd><p>  See <a href="#INCLUDE-AND-EXCLUDE" title="INCLUDE AND EXCLUDE" data-bare-link="true">INCLUDE AND EXCLUDE</a>.</p></dd>
+<dt><code>-X</code> <var>paths</var> <code>--exclude=</code><var>paths</var></dt><dd><p>  See <a href="#INCLUDE-AND-EXCLUDE" title="INCLUDE AND EXCLUDE" data-bare-link="true">INCLUDE AND EXCLUDE</a>.</p></dd>
+<dt><code>--include-ref</code>=<var>refname</var></dt><dd><p>  See [INCLUDE AND EXCLUDE (REFS)].</p></dd>
+<dt><code>--exclude-ref</code>=<var>refname</var></dt><dd><p>  See [INCLUDE AND EXCLUDE (REFS)].</p></dd>
+<dt><code>--skip-fetch</code></dt><dd><p>  Assumes that the known set of remote references is complete, and should not
+  be refreshed when determining the set of "un-pushed" commits to migrate. Has
+  no effect when combined with <code>--include-ref</code> or <code>--exclude-ref</code>.</p></dd>
+<dt><code>--everything</code></dt><dd><p>  See [INCLUDE AND EXCLUDE (REFS)].</p>
+
+<p>  Note: Git refs are "case-sensitive" on all platforms in "packed from" (see
+  <code>git-pack-refs(1)</code>). On "case-insensitive" file systems, e.g. NTFS on Windows
+  or default APFS on macOS, <code>git-lfs-migrate(1)</code> would only migrate the first
+  ref if two or more refs are equal except for upper/lower case letters.</p></dd>
+<dt class="flush"><code>--yes</code></dt><dd><p>  Assume a yes answer to any prompts, permitting noninteractive use.
+  Currently, the only such prompt is the one asking whether to overwrite
+  (destroy) any working copy changes. Thus, specifying this option may cause
+  data loss if you are not careful.</p></dd>
+<dt>[branch ...]</dt><dd><p>  Migrate only the set of branches listed. If not given, <code>git-lfs-migrate(1)</code>
+  will migrate the currently checked out branch.</p>
+
+<p>  References beginning with <code>^</code> will be excluded, whereas branches that do not
+  begin with <code>^</code> will be included.</p>
+
+<p>  If any of <code>--include-ref</code> or <code>--exclude-ref</code> are given, the checked out
+  branch will not be appended, but branches given explicitly will be appended.</p></dd>
+</dl>
+
+
+<h3 id="INFO">INFO</h3>
+
+<p>The <code>info</code> mode summarizes the sizes of file objects present in the Git history.
+It supports all the core <code>migrate</code> options and these additional ones:</p>
+
+<ul>
+<li><p><code>--above=&lt;size></code>
+  Only count files whose individual filesize is above the given size. <code>size</code>
+  may be specified as a number of bytes, or a number followed by a storage
+  unit, e.g., "1b", "20 MB", "3 TiB", etc.</p>
+
+<p>  If a set of files sharing a common extension has no files in that set whose
+  individual size is above the given <code>--above</code> no files no entry for that set
+  will be shown.</p></li>
+<li><p><code>--top=&lt;n></code>
+  Only display the top <code>n</code> entries, ordered by how many total files match the
+  given pathspec.  The default is to show only the top 5 entries.  When
+  existing Git LFS objects are found, an extra, separate "LFS Objects" line
+  is output in addition to the top <code>n</code> entries, unless the <code>--pointers</code>
+  option is used to change this behavior.</p></li>
+<li><p><code>--unit=&lt;unit></code>
+  Format the number of bytes in each entry as a quantity of the storage unit
+  provided. Valid units include:</p>
+
+<pre><code>* b, kib, mib, gib, tib, pib - for IEC storage units
+* b, kb, mb, gb, tb, pb - for SI storage units
+</code></pre>
+
+<p>  If a <code>--unit</code> is not specified, the largest unit that can fit the number of
+  counted bytes as a whole number quantity is chosen.</p></li>
+<li><p><code>--pointers=[follow|no-follow|ignore]</code>
+  Treat existing Git LFS pointers in the history according to one of three
+  alternatives.  In the default <code>follow</code> case, if any pointers are found,
+  an additional separate "LFS Objects" line item is output which summarizes
+  the total number and size of the Git LFS objects referenced by pointers.
+  In the <code>ignore</code> case, any pointers are simply ignored, while the <code>no-follow</code>
+  case replicates the behavior of the <code>info</code> mode in older Git LFS versions
+  and treats any pointers it finds as if they were regular files, so the
+  output totals only include the contents of the pointers, not the contents
+  of the objects to which they refer.</p></li>
+<li><p><code>--fixup</code>
+  Infer <code>--include</code> and <code>--exclude</code> filters on a per-commit basis based on the
+  .gitattributes files in a repository. In practice, this option counts any
+  filepaths which should be tracked by Git LFS according to the repository's
+  .gitattributes file(s), but aren't already pointers. The .gitattributes
+  files are not reported, in contrast to the normal output of the <code>info</code> mode.
+  This option is incompatible with explicitly given <code>--include</code>, <code>--exclude</code>
+  filters and with any <code>--pointers</code> setting other than <code>ignore</code>, hence
+  <code>--fixup</code> implies <code>--pointers=ignore</code> if it is not explicitly set.</p></li>
+</ul>
+
+
+<p>The format of the output shows the filename pattern, the total size of the
+file objects (excluding those below the <code>--above</code> threshold, if one was
+defined), and the ratio of the number of files above the threshold to the
+total number of files; this ratio is also shown as a percentage.  For example:</p>
+
+<pre><code>*.gif               93 MB   9480/10504 files(s)  90%
+*.png               14 MB    1732/1877 files(s)  92%
+</code></pre>
+
+<p>By default only the top five entries are shown, but <code>--top</code> allows for
+more or fewer to be output as desired.</p>
+
+<h3 id="IMPORT">IMPORT</h3>
+
+<p>The <code>import</code> mode migrates objects present in the Git history to pointer
+files tracked and stored with Git LFS. It supports all the core <code>migrate</code>
+options and these additional ones:</p>
+
+<ul>
+<li><p><code>--verbose</code>
+  Print the commit oid and filename of migrated files to STDOUT.</p></li>
+<li><p><code>--above=&lt;size></code>
+  Only migrate files whose individual filesize is above the given size. <code>size</code>
+  may be specified as a number of bytes, or a number followed by a storage
+  unit, e.g., "1b", "20 MB", "3 TiB", etc.</p></li>
+<li><p><code>--object-map=&lt;path></code>
+  Write to <code>path</code> a file with the mapping of each rewritten commits. The file
+  format is CSV with this pattern: <code>OLD-SHA</code>,<code>NEW-SHA</code></p></li>
+<li><p><code>--no-rewrite</code>
+  Migrate objects to Git LFS in a new commit without rewriting Git
+  history. Please note that when this option is used, the <code>migrate import</code>
+  command will expect a different argument list, specialized options will
+  become available, and the core <code>migrate</code> options will be ignored. See
+  [IMPORT (NO REWRITE)].</p></li>
+<li><p><code>--fixup</code>
+  Infer <code>--include</code> and <code>--exclude</code> filters on a per-commit basis based on the
+  <code>.gitattributes</code> files in a repository. In practice, this option imports any
+  filepaths which should be tracked by Git LFS according to the repository's
+  <code>.gitattributes</code> file(s), but aren't already pointers. This option is
+  incompatible with explicitly given <code>--include</code>, <code>--exclude</code> filters.</p></li>
+</ul>
+
+
+<p>If <code>--no-rewrite</code> is not provided and <code>--include</code> or <code>--exclude</code> (<code>-I</code>, <code>-X</code>,
+respectively) are given, the <code>.gitattributes</code> will be modified to include any
+new filepath patterns as given by those flags.</p>
+
+<p>If <code>--no-rewrite</code> is not provided and neither of those flags are given, the
+gitattributes will be incrementally modified to include new filepath extensions
+as they are rewritten in history.</p>
+
+<h3 id="IMPORT-NO-REWRITE-">IMPORT (NO REWRITE)</h3>
+
+<p>The <code>import</code> mode has a special sub-mode enabled by the <code>--no-rewrite</code> flag.
+This sub-mode will migrate objects to pointers as in the base <code>import</code>
+mode, but will do so in a new commit without rewriting Git history. When using
+this sub-mode, the base <code>migrate</code> options, such as <code>--include-ref</code>, will be
+ignored, as will those for the base <code>import</code> mode. The <code>migrate</code> command will
+also take a different argument list. As a result of these changes,
+<code>--no-rewrite</code> will only operate on the current branch - any other interested
+branches must have the generated commit merged in.</p>
+
+<p>The <code>--no-rewrite</code> sub-mode supports the following options and arguments:</p>
+
+<ul>
+<li><p><code>-m &lt;message> --message=&lt;message></code>
+  Specifies a commit message for the newly created commit.</p></li>
+<li><p>[file ...]
+  The list of files to import. These files must be tracked by patterns
+  specified in the gitattributes.</p></li>
+</ul>
+
+
+<p>If <code>--message</code> is given, the new commit will be created with the provided
+message. If no message is given, a commit message will be generated based on the
+file arguments.</p>
+
+<h3 id="EXPORT">EXPORT</h3>
+
+<p>The <code>export</code> mode migrates Git LFS pointer files present in the Git history out
+of Git LFS, converting them into their corresponding object files. It supports
+all the core <code>migrate</code> options and these additional ones:</p>
+
+<ul>
+<li><p><code>--verbose</code>
+  Print the commit oid and filename of migrated files to STDOUT.</p></li>
+<li><p><code>--object-map=&lt;path></code>
+  Write to <code>path</code> a file with the mapping of each rewritten commit. The file
+  format is CSV with this pattern: <code>OLD-SHA</code>,<code>NEW-SHA</code></p></li>
+<li><p><code>--remote=&lt;git-remote></code>
+  Download LFS objects from the provided <code>git-remote</code> during the export. If
+  not provided, defaults to <code>origin</code>.</p></li>
+</ul>
+
+
+<p>The <code>export</code> mode requires at minimum a pattern provided with the <code>--include</code>
+argument to specify which files to export. Files matching the <code>--include</code>
+patterns will be removed from Git LFS, while files matching the <code>--exclude</code>
+patterns will retain their Git LFS status. The export command will modify the
+<code>.gitattributes</code> to set/unset any filepath patterns as given by those flags.</p>
+
+<h2 id="INCLUDE-AND-EXCLUDE">INCLUDE AND EXCLUDE</h2>
+
+<p>You can specify that <code>git lfs migrate</code> should only convert files whose
+pathspec matches the <code>--include</code> glob patterns and does not match the
+<code>--exclude</code> glob patterns, either to reduce total migration time or to only
+migrate part of your repo.  Multiple patterns may be given using commas
+as delimiters.</p>
+
+<p>Pattern matching is done so as to be functionally equivalent to the pattern
+matching format of <code>.gitattributes</code>.  In addition to simple file extension
+matches (e.g., <code>*.gif</code>) patterns may also specify directory paths, in which
+case the <code>path/**</code> format may be used to match recursively.</p>
+
+<h2 id="INCLUDE-AND-EXCLUDE-REFS-">INCLUDE AND EXCLUDE (REFS)</h2>
+
+<p>You can specify that <code>git lfs migrate</code> should only convert files added
+in commits reachable from certain references, namely those defined using one
+or more <code>--include-ref</code> options, and should ignore files in commits reachable
+from references defined in <code>--exclude-ref</code> options.</p>
+
+<pre><code>        D---E---F
+       /         \
+  A---B------C    refs/heads/my-feature
+   \          \
+    \          refs/heads/main
+     \
+      refs/remotes/origin/main
+</code></pre>
+
+<p>In the above configuration, the following commits are reachable by each ref:</p>
+
+<pre><code>refs/heads/main:           C, B, A
+refs/heads/my-feature:     F, E, D, B, A
+refs/remote/origin/main:   A
+</code></pre>
+
+<p>The following <code>git lfs migrate</code> options would, therefore, include commits
+F, E, D, C, and B, but exclude commit A:</p>
+
+<pre><code>  --include-ref=refs/heads/my-feature
+  --include-ref=refs/heads/main
+  --exclude-ref=refs/remotes/origin/main
+</code></pre>
+
+<p>The presence of flag <code>--everything</code> indicates that all local and remote
+references should be migrated.</p>
+
+<h2 id="EXAMPLES">EXAMPLES</h2>
+
+<h3 id="Migrate-unpushed-commits">Migrate unpushed commits</h3>
+
+<p>A common use case for the migrate command is to convert large Git objects to
+LFS before pushing your commits. By default, it only scans commits that don't
+exist on any remote, so long as the repository is non-bare.</p>
+
+<p>First, run <code>git lfs migrate info</code> to list the file types taking up the most
+space in your repository:</p>
+
+<pre><code>$ git lfs migrate info
+migrate: Fetching remote refs: ..., done
+migrate: Sorting commits: ..., done
+migrate: Examining commits: 100% (1/1), done
+*.mp3   284 MB    1/1 files(s)  100%
+*.pdf   42 MB     8/8 files(s)  100%
+*.psd   9.8 MB  15/15 files(s)  100%
+*.ipynb 6.9 MB    6/6 files(s)  100%
+*.csv   5.8 MB    2/2 files(s)  100%
+</code></pre>
+
+<p>Now, you can run <code>git lfs migrate import</code> to convert some file types to LFS:</p>
+
+<pre><code>$ git lfs migrate import --include="*.mp3,*.psd"
+migrate: Fetching remote refs: ..., done
+migrate: Sorting commits: ..., done
+migrate: Rewriting commits: 100% (1/1), done
+  main  d2b959babd099fe70da1c1512e2475e8a24de163 -&gt; 136e706bf1ae79643915c134e17a6c933fd53c61
+migrate: Updating refs: ..., done
+</code></pre>
+
+<p>If after conversion you find that some files in your working directory have
+been replaced with Git LFS pointers, this is normal, and the working copies
+of these files can be repopulated with their full expected contents by using
+<code>git lfs checkout</code>.</p>
+
+<h3 id="Migrate-local-history">Migrate local history</h3>
+
+<p>You can also migrate the entire history of your repository:</p>
+
+<pre><code># Check for large files and existing Git LFS objects in your local main branch
+$ git lfs migrate info --include-ref=main
+
+# Check for large files and existing Git LFS objects in every branch
+$ git lfs migrate info --everything
+
+# Check for large files in every branch, ignoring any existing Git LFS objects,
+# and listing the top 100 or fewer results
+$ git lfs migrate info --everything --pointers=ignore --top=100
+</code></pre>
+
+<p>The same flags will work in <code>import</code> mode:</p>
+
+<pre><code># Convert all zip files in your main branch
+$ git lfs migrate import --include-ref=main --include="*.zip"
+
+# Convert all zip files in every local branch
+$ git lfs migrate import --everything --include="*.zip"
+
+# Convert all files over 100K in every local branch
+$ git lfs migrate import --everything --above=100Kb
+</code></pre>
+
+<p>Note: This will require a force-push to any existing Git remotes.  Using
+the <code>--all</code> option when force-pushing may be convenient if many refs were
+updated, e.g., after importing to Git LFS with the <code>--everything</code> option.</p>
+
+<h3 id="Migrate-without-rewriting-local-history">Migrate without rewriting local history</h3>
+
+<p>You can also migrate files without modifying the existing history of your
+repository. Note that in the examples below, files in subdirectories are not
+included because they are not explicitly specified.</p>
+
+<p>Without a specified commit message:</p>
+
+<pre><code>$ git lfs migrate import --no-rewrite test.zip *.mp3 *.psd
+</code></pre>
+
+<p>With a specified commit message:</p>
+
+<pre><code>$ git lfs migrate import --no-rewrite \
+  -m "Import test.zip, .mp3, .psd files in root of repo" \
+  test.zip *.mp3 *.psd
+</code></pre>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><span class="man-ref">git-lfs-checkout<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-track<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-untrack<span class="s">(1)</span></span>, <span class="man-ref">gitattributes<span class="s">(5)</span></span>.</p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-migrate(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-pointer.1

@@ -0,0 +1,48 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-POINTER" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-pointer\fR \- Build, compare, and check pointers
+.
+.SH "SYNOPSIS"
+\fBgit lfs pointer \-\-file=path/to/file\fR
+.
+.br
+\fBgit lfs pointer \-\-file=path/to/file \-\-pointer=path/to/pointer\fR
+.
+.br
+\fBgit lfs pointer \-\-file=path/to/file \-\-stdin\fR \fBgit lfs pointer \-\-check \-\-file=path/to/file\fR
+.
+.SH "Description"
+Builds and optionally compares generated pointer files to ensure consistency between different Git LFS implementations\.
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-\-file\fR
+A local file to build the pointer from\.
+.
+.TP
+\fB\-\-pointer\fR
+A local file including the contents of a pointer generated from another implementation\. This is compared to the pointer generated from \fB\-\-file\fR\.
+.
+.TP
+\fB\-\-stdin\fR
+Reads the pointer from STDIN to compare with the pointer generated from \fB\-\-file\fR\.
+.
+.TP
+\fB\-\-check\fR
+Reads the pointer from STDIN (if \fB\-\-stdin\fR is given) or the filepath (if \fB\-\-file\fR) is given\. If neither or both of \fB\-\-stdin\fR and \fB\-\-file\fR are given, the invocation is invalid\. Exits 0 if the data read is a valid Git LFS pointer\. Exits 1 otherwise\.
+.
+.TP
+\fB\-\-strict\fR:
+
+.
+.TP
+\fB\-\-no\-strict\fR
+In conjunction with \fB\-\-check\fR, \fB\-\-strict\fR verifies that the pointer is canonical; that is, it would be the one created by Git LFS\. If it is not, exits 2\. The default, for backwards compatibility, is \fB\-\-no\-strict\fR, but this may change in a future version\.
+.
+.SH "SEE ALSO"
+Part of the git\-lfs(1) suite\.

man/git-lfs-pointer.1.html

@@ -0,0 +1,119 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-pointer(1) - Build, compare, and check pointers</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#Description">Description</a>
+    <a href="#OPTIONS">OPTIONS</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-pointer(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-pointer(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-pointer</code> - <span class="man-whatis">Build, compare, and check pointers</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs pointer --file=path/to/file</code><br />
+<code>git lfs pointer --file=path/to/file --pointer=path/to/pointer</code><br />
+<code>git lfs pointer --file=path/to/file --stdin</code>
+<code>git lfs pointer --check --file=path/to/file</code></p>
+
+<h2 id="Description">Description</h2>
+
+<p>Builds and optionally compares generated pointer files to ensure consistency
+between different Git LFS implementations.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<dl>
+<dt class="flush"><code>--file</code></dt><dd><p>  A local file to build the pointer from.</p></dd>
+<dt><code>--pointer</code></dt><dd><p>  A local file including the contents of a pointer generated from another
+  implementation.  This is compared to the pointer generated from <code>--file</code>.</p></dd>
+<dt class="flush"><code>--stdin</code></dt><dd><p>  Reads the pointer from STDIN to compare with the pointer generated from
+  <code>--file</code>.</p></dd>
+<dt class="flush"><code>--check</code></dt><dd><p>  Reads the pointer from STDIN (if <code>--stdin</code> is given) or the filepath (if
+  <code>--file</code>) is given. If neither or both of <code>--stdin</code> and <code>--file</code> are given,
+  the invocation is invalid. Exits 0 if the data read is a valid Git LFS
+  pointer. Exits 1 otherwise.</p></dd>
+<dt><code>--strict</code>:</dt><dd><p></p></dd>
+<dt><code>--no-strict</code></dt><dd>  In conjunction with <code>--check</code>, <code>--strict</code> verifies that the pointer is
+  canonical; that is, it would be the one created by Git LFS.  If it is not,
+  exits 2.  The default, for backwards compatibility, is <code>--no-strict</code>, but
+  this may change in a future version.</dd>
+</dl>
+
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-pointer(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-post-checkout.1

@@ -0,0 +1,19 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-POST\-CHECKOUT" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-post\-checkout\fR \- Git post\-checkout hook implementation
+.
+.SH "SYNOPSIS"
+\fBgit lfs post\-checkout\fR \fIrev_before\fR \fIref_after\fR \fIis_branch_checkout\fR
+.
+.SH "DESCRIPTION"
+Responds to Git post\-checkout events\. It makes sure that any files which are marked as lockable by \fBgit lfs track\fR are read\-only in the working copy, if not currently locked by the local user\.
+.
+.SH "SEE ALSO"
+git\-lfs\-track(1)
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-post-checkout.1.html

@@ -0,0 +1,98 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-post-checkout(1) - Git post-checkout hook implementation</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-post-checkout(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-post-checkout(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-post-checkout</code> - <span class="man-whatis">Git post-checkout hook implementation</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs post-checkout</code> <var>rev_before</var> <var>ref_after</var> <var>is_branch_checkout</var></p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Responds to Git post-checkout events. It makes sure that any files which are
+marked as lockable by <code>git lfs track</code> are read-only in the working copy, if
+not currently locked by the local user.</p>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><span class="man-ref">git-lfs-track<span class="s">(1)</span></span></p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-post-checkout(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-post-commit.1

@@ -0,0 +1,22 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-POST\-COMMIT" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-post\-commit\fR \- Git post\-commit hook implementation
+.
+.SH "SYNOPSIS"
+\fBgit lfs post\-commit\fR
+.
+.SH "DESCRIPTION"
+Responds to Git post\-commit events\. It makes sure that any files which are marked as lockable by \fBgit lfs track\fR are read\-only in the working copy, if not currently locked by the local user\.
+.
+.P
+Where the \fBgit lfs post\-merge\fR command, which has a similar purpose, must examine all files in the working copy, \fBgit lfs post\-commit\fR can limit itself checking only those files which have changed in \fBHEAD\fR\. It primarily handles newly added lockable files which have not yet been made read\-only\.
+.
+.SH "SEE ALSO"
+git\-lfs\-post\-merge(1), git\-lfs\-track(1)
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-post-commit.1.html

@@ -0,0 +1,103 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-post-commit(1) - Git post-commit hook implementation</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-post-commit(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-post-commit(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-post-commit</code> - <span class="man-whatis">Git post-commit hook implementation</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs post-commit</code></p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Responds to Git post-commit events. It makes sure that any files which are
+marked as lockable by <code>git lfs track</code> are read-only in the working copy, if
+not currently locked by the local user.</p>
+
+<p>Where the <code>git lfs post-merge</code> command, which has a similar purpose, must
+examine all files in the working copy, <code>git lfs post-commit</code> can limit
+itself checking only those files which have changed in <code>HEAD</code>.  It primarily
+handles newly added lockable files which have not yet been made read-only.</p>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><span class="man-ref">git-lfs-post-merge<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-track<span class="s">(1)</span></span></p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-post-commit(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-post-merge.1

@@ -0,0 +1,19 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-POST\-MERGE" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-post\-merge\fR \- Git post\-merge hook implementation
+.
+.SH "SYNOPSIS"
+\fBgit lfs post\-merge\fR \fIis_squash\fR
+.
+.SH "DESCRIPTION"
+Responds to Git post\-merge events\. It makes sure that any files which are marked as lockable by \fBgit lfs track\fR are read\-only in the working copy, if not currently locked by the local user\.
+.
+.SH "SEE ALSO"
+git\-lfs\-track(1)
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-post-merge.1.html

@@ -0,0 +1,98 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-post-merge(1) - Git post-merge hook implementation</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-post-merge(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-post-merge(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-post-merge</code> - <span class="man-whatis">Git post-merge hook implementation</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs post-merge</code> <var>is_squash</var></p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Responds to Git post-merge events. It makes sure that any files which are
+marked as lockable by <code>git lfs track</code> are read-only in the working copy, if
+not currently locked by the local user.</p>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><span class="man-ref">git-lfs-track<span class="s">(1)</span></span></p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-post-merge(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-pre-push.1

@@ -0,0 +1,47 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-PRE\-PUSH" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-pre\-push\fR \- Git pre\-push hook implementation
+.
+.SH "SYNOPSIS"
+\fBgit lfs pre\-push\fR \fIremote\fR [remoteurl]
+.
+.SH "DESCRIPTION"
+Responds to Git pre\-hook events\. It reads the range of commits from STDIN, in the following format:
+.
+.IP "" 4
+.
+.nf
+
+<local\-ref> SP <local\-sha1> SP <remote\-ref> SP <remote\-sha1> \en
+.
+.fi
+.
+.IP "" 0
+.
+.P
+It also takes the remote name and URL as arguments\.
+.
+.P
+If any of those Git objects are associated with Git LFS objects, those objects will be pushed to the Git LFS API\.
+.
+.P
+In the case of pushing a new branch, the list of Git objects will be all of the Git objects in this branch\.
+.
+.P
+In the case of deleting a branch, no attempts to push Git LFS objects will be made\.
+.
+.SH "OPTIONS"
+.
+.TP
+\fBGIT_LFS_SKIP_PUSH\fR
+Do nothing on pre\-push\. For more, see: git\-lfs\-config(5)\.
+.
+.SH "SEE ALSO"
+git\-lfs\-clean(1), git\-lfs\-push(1)\.
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-pre-push.1.html

@@ -0,0 +1,119 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-pre-push(1) - Git pre-push hook implementation</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#OPTIONS">OPTIONS</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-pre-push(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-pre-push(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-pre-push</code> - <span class="man-whatis">Git pre-push hook implementation</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs pre-push</code> <var>remote</var> [remoteurl]</p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Responds to Git pre-hook events. It reads the range of commits from STDIN, in
+the following format:</p>
+
+<pre><code>&lt;local-ref> SP &lt;local-sha1> SP &lt;remote-ref> SP &lt;remote-sha1> \n
+</code></pre>
+
+<p>It also takes the remote name and URL as arguments.</p>
+
+<p>If any of those Git objects are associated with Git LFS objects, those
+objects will be pushed to the Git LFS API.</p>
+
+<p>In the case of pushing a new branch, the list of Git objects will be all of
+the Git objects in this branch.</p>
+
+<p>In the case of deleting a branch, no attempts to push Git LFS objects will be
+made.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<dl>
+<dt><code>GIT_LFS_SKIP_PUSH</code></dt><dd>  Do nothing on pre-push. For more, see: <span class="man-ref">git-lfs-config<span class="s">(5)</span></span>.</dd>
+</dl>
+
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><span class="man-ref">git-lfs-clean<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-push<span class="s">(1)</span></span>.</p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-pre-push(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-prune.1

@@ -0,0 +1,123 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-PRUNE" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-prune\fR \- Delete old LFS files from local storage
+.
+.SH "SYNOPSIS"
+\fBgit lfs prune\fR \fIoptions\fR
+.
+.SH "DESCRIPTION"
+Deletes local copies of LFS files which are old, thus freeing up disk space\. Prune operates by enumerating all the locally stored objects, and then deleting any which are not referenced by at least ONE of the following:
+.
+.IP "\(bu" 4
+the current checkout
+.
+.IP "\(bu" 4
+all existing stashes
+.
+.IP "\(bu" 4
+a \'recent branch\'; see \fIRECENT FILES\fR
+.
+.IP "\(bu" 4
+a \'recent commit\' on the current branch or recent branches; see \fIRECENT FILES\fR
+.
+.IP "\(bu" 4
+a commit which has not been pushed; see \fIUNPUSHED LFS FILES\fR
+.
+.IP "\(bu" 4
+any other worktree checkouts; see git\-worktree(1)
+.
+.IP "" 0
+.
+.P
+In general terms, prune will delete files you\'re not currently using and which are not \'recent\', so long as they\'ve been pushed i\.e\. the local copy is not the only one\.
+.
+.P
+The reflog is not considered, only commits\. Therefore LFS objects that are only referenced by orphaned commits are always deleted\.
+.
+.P
+Note: you should not run \fBgit lfs prune\fR if you have different repositories sharing the same custom storage directory; see git\-lfs\-config(1) for more details about \fBlfs\.storage\fR option\.
+.
+.SH "OPTIONS"
+.
+.IP "\(bu" 4
+\fB\-\-dry\-run\fR \fB\-d\fR Don\'t actually delete anything, just report on what would have been done
+.
+.IP "\(bu" 4
+\fB\-\-force\fR \fB\-f\fR Prune all objects except unpushed objects, including objects required for currently checked out refs\. Implies \fB\-\-recent\fR\.
+.
+.IP "\(bu" 4
+\fB\-\-recent\fR Prune even objects that would normally be preserved by the configuration options specified below in \fIRECENT FILES\fR\.
+.
+.IP "\(bu" 4
+\fB\-\-verify\-remote\fR \fB\-c\fR Contact the remote and check that copies of the files we would delete definitely exist before deleting\. See \fIVERIFY REMOTE\fR\.
+.
+.IP "\(bu" 4
+\fB\-\-no\-verify\-remote\fR Disables remote verification if lfs\.pruneverifyremotealways was enabled in settings\. See \fIVERIFY REMOTE\fR\.
+.
+.IP "\(bu" 4
+\fB\-\-verbose\fR \fB\-v\fR Report the full detail of what is/would be deleted\.
+.
+.IP "" 0
+.
+.SH "RECENT FILES"
+Prune won\'t delete LFS files referenced by \'recent\' commits, in case you want to use them again without having to download\. The definition of \'recent\' is derived from the one used by git\-lfs\-fetch(1) to download recent objects with the \fB\-\-recent\fR option, with an offset of a number of days (default 3) to ensure that we always keep files you download for a few days\.
+.
+.P
+Here are the git\-config(1) settings that control this behaviour:
+.
+.IP "\(bu" 4
+\fBlfs\.pruneoffsetdays\fR
+.
+.br
+The number of extra days added to the fetch recent settings when using them to decide when to prune\. So for a reference to be considered old enough to prune, it has to be this many days older than the oldest reference that would be downloaded via \fBgit lfs fetch \-\-recent\fR\. Only used if the relevant fetch recent \'days\' setting is non\-zero\. Default 3 days\.
+.
+.IP "\(bu" 4
+\fBlfs\.fetchrecentrefsdays\fR
+.
+.br
+\fBlfs\.fetchrecentremoterefs\fR
+.
+.br
+\fBlfs\.fetchrecentcommitsdays\fR
+.
+.br
+These have the same meaning as git\-lfs\-fetch(1) with the \fB\-\-recent\fR option, they are used as a base for the offset above\. Anything which falls outside of this offsetted window is considered old enough to prune\. If a day value is zero, that condition is not used at all to retain objects and they will be pruned\.
+.
+.IP "" 0
+.
+.SH "UNPUSHED LFS FILES"
+When the only copy of an LFS file is local, and it is still reachable from any reference, that file can never be pruned, regardless of how old it is\.
+.
+.P
+To determine whether an LFS file has been pushed, we check the difference between local refs and remote refs; where the local ref is ahead, any LFS files referenced in those commits is unpushed and will not be deleted\. This works because the LFS pre\-push hook always ensures that LFS files are pushed before the remote branch is updated\.
+.
+.P
+See \fIDEFAULT REMOTE\fR, for which remote is considered \'pushed\' for pruning purposes\.
+.
+.SH "VERIFY REMOTE"
+The \fB\-\-verify\-remote\fR option calls the remote to ensure that any LFS files to be deleted have copies on the remote before actually deleting them\.
+.
+.P
+Usually the check performed by \fIUNPUSHED LFS FILES\fR is enough to determine that files have been pushed, but if you want to be extra sure at the expense of extra overhead you can make prune actually call the remote API and verify the presence of the files you\'re about to delete locally\. See \fIDEFAULT REMOTE\fR for which remote is checked\.
+.
+.P
+You can make this behaviour the default by setting \fBlfs\.pruneverifyremotealways\fR to true\.
+.
+.P
+In addition to the overhead of calling the remote, using this option also requires prune to distinguish between totally unreachable files (e\.g\. those that were added to the index but never committed, or referenced only by orphaned commits), and files which are still referenced, but by commits which are prunable\. This makes the prune process take longer\.
+.
+.SH "DEFAULT REMOTE"
+When identifying \fIUNPUSHED LFS FILES\fR and performing \fIVERIFY REMOTE\fR, a single remote, \'origin\', is normally used as the reference\. This one remote is considered canonical; even if you use multiple remotes, you probably want to retain your local copies until they\'ve made it to that remote\. \'origin\' is used by default because that will usually be a main central repo, or your fork of it \- in both cases that\'s a valid remote backup of your work\. If origin doesn\'t exist then by default nothing will be pruned because everything is treated as \'unpushed\'\.
+.
+.P
+You can alter the remote via git config: \fBlfs\.pruneremotetocheck\fR\. Set this to a different remote name to check that one instead of \'origin\'\.
+.
+.SH "SEE ALSO"
+git\-lfs\-fetch(1)
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-prune.1.html

@@ -0,0 +1,222 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-prune(1) - Delete old LFS files from local storage</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#OPTIONS">OPTIONS</a>
+    <a href="#RECENT-FILES">RECENT FILES</a>
+    <a href="#UNPUSHED-LFS-FILES">UNPUSHED LFS FILES</a>
+    <a href="#VERIFY-REMOTE">VERIFY REMOTE</a>
+    <a href="#DEFAULT-REMOTE">DEFAULT REMOTE</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-prune(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-prune(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-prune</code> - <span class="man-whatis">Delete old LFS files from local storage</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs prune</code> <a href="#OPTIONS" title="OPTIONS" data-bare-link="true">options</a></p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Deletes local copies of LFS files which are old, thus freeing up disk space.
+Prune operates by enumerating all the locally stored objects, and then deleting
+any which are not referenced by at least ONE of the following:</p>
+
+<ul>
+<li>the current checkout</li>
+<li>all existing stashes</li>
+<li>a 'recent branch'; see <a href="#RECENT-FILES" title="RECENT FILES" data-bare-link="true">RECENT FILES</a></li>
+<li>a 'recent commit' on the current branch or recent branches; see <a href="#RECENT-FILES" title="RECENT FILES" data-bare-link="true">RECENT FILES</a></li>
+<li>a commit which has not been pushed; see <a href="#UNPUSHED-LFS-FILES" title="UNPUSHED LFS FILES" data-bare-link="true">UNPUSHED LFS FILES</a></li>
+<li>any other worktree checkouts; see <span class="man-ref">git-worktree<span class="s">(1)</span></span></li>
+</ul>
+
+
+<p>In general terms, prune will delete files you're not currently using and which
+are not 'recent', so long as they've been pushed i.e. the local copy is not the
+only one.</p>
+
+<p>The reflog is not considered, only commits. Therefore LFS objects that are
+only referenced by orphaned commits are always deleted.</p>
+
+<p>Note: you should not run <code>git lfs prune</code> if you have different repositories
+sharing the same custom storage directory; see <span class="man-ref">git-lfs-config<span class="s">(1)</span></span> for more
+details about <code>lfs.storage</code> option.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<ul>
+<li><p><code>--dry-run</code> <code>-d</code>
+Don't actually delete anything, just report on what would have been done</p></li>
+<li><p><code>--force</code> <code>-f</code>
+Prune all objects except unpushed objects, including objects required for
+currently checked out refs.  Implies <code>--recent</code>.</p></li>
+<li><p><code>--recent</code>
+Prune even objects that would normally be preserved by the configuration
+options specified below in <a href="#RECENT-FILES" title="RECENT FILES" data-bare-link="true">RECENT FILES</a>.</p></li>
+<li><p><code>--verify-remote</code> <code>-c</code>
+Contact the remote and check that copies of the files we would delete
+definitely exist before deleting. See <a href="#VERIFY-REMOTE" title="VERIFY REMOTE" data-bare-link="true">VERIFY REMOTE</a>.</p></li>
+<li><p><code>--no-verify-remote</code>
+Disables remote verification if lfs.pruneverifyremotealways was enabled in
+settings. See <a href="#VERIFY-REMOTE" title="VERIFY REMOTE" data-bare-link="true">VERIFY REMOTE</a>.</p></li>
+<li><p><code>--verbose</code> <code>-v</code>
+Report the full detail of what is/would be deleted.</p></li>
+</ul>
+
+
+<h2 id="RECENT-FILES">RECENT FILES</h2>
+
+<p>Prune won't delete LFS files referenced by 'recent' commits, in case you want
+to use them again without having to download. The definition of 'recent' is
+derived from the one used by <span class="man-ref">git-lfs-fetch<span class="s">(1)</span></span> to download recent objects with
+the <code>--recent</code> option, with an offset of a number of days (default 3) to ensure
+that we always keep files you download for a few days.</p>
+
+<p>Here are the <span class="man-ref">git-config<span class="s">(1)</span></span> settings that control this behaviour:</p>
+
+<ul>
+<li><p><code>lfs.pruneoffsetdays</code> <br />
+The number of extra days added to the fetch recent settings when using them
+to decide when to prune. So for a reference to be considered old enough to
+prune, it has to be this many days older than the oldest reference that would
+be downloaded via <code>git lfs fetch --recent</code>. Only used if the relevant
+fetch recent 'days' setting is non-zero. Default 3 days.</p></li>
+<li><p><code>lfs.fetchrecentrefsdays</code> <br />
+<code>lfs.fetchrecentremoterefs</code> <br />
+<code>lfs.fetchrecentcommitsdays</code> <br />
+These have the same meaning as <span class="man-ref">git-lfs-fetch<span class="s">(1)</span></span> with the <code>--recent</code> option,
+they are used as a base for the offset above. Anything which falls outside
+of this offsetted window is considered old enough to prune. If a day value is
+zero, that condition is not used at all to retain objects and they will be
+pruned.</p></li>
+</ul>
+
+
+<h2 id="UNPUSHED-LFS-FILES">UNPUSHED LFS FILES</h2>
+
+<p>When the only copy of an LFS file is local, and it is still reachable from any
+reference, that file can never be pruned, regardless of how old it is.</p>
+
+<p>To determine whether an LFS file has been pushed, we check the difference
+between local refs and remote refs; where the local ref is ahead, any LFS files
+referenced in those commits is unpushed and will not be deleted. This works
+because the LFS pre-push hook always ensures that LFS files are pushed before
+the remote branch is updated.</p>
+
+<p>See <a href="#DEFAULT-REMOTE" title="DEFAULT REMOTE" data-bare-link="true">DEFAULT REMOTE</a>, for which remote is considered 'pushed' for pruning
+purposes.</p>
+
+<h2 id="VERIFY-REMOTE">VERIFY REMOTE</h2>
+
+<p>The <code>--verify-remote</code> option calls the remote to ensure that any LFS files to be
+deleted have copies on the remote before actually deleting them.</p>
+
+<p>Usually the check performed by <a href="#UNPUSHED-LFS-FILES" title="UNPUSHED LFS FILES" data-bare-link="true">UNPUSHED LFS FILES</a> is enough to determine that
+files have been pushed, but if you want to be extra sure at the expense of extra
+overhead you can make prune actually call the remote API and verify the
+presence of the files you're about to delete locally. See <a href="#DEFAULT-REMOTE" title="DEFAULT REMOTE" data-bare-link="true">DEFAULT REMOTE</a> for
+which remote is checked.</p>
+
+<p>You can make this behaviour the default by setting <code>lfs.pruneverifyremotealways</code>
+to true.</p>
+
+<p>In addition to the overhead of calling the remote, using this option also
+requires prune to distinguish between totally unreachable files (e.g. those that
+were added to the index but never committed, or referenced only by orphaned
+commits), and files which are still referenced, but by commits which are
+prunable. This makes the prune process take longer.</p>
+
+<h2 id="DEFAULT-REMOTE">DEFAULT REMOTE</h2>
+
+<p>When identifying <a href="#UNPUSHED-LFS-FILES" title="UNPUSHED LFS FILES" data-bare-link="true">UNPUSHED LFS FILES</a> and performing <a href="#VERIFY-REMOTE" title="VERIFY REMOTE" data-bare-link="true">VERIFY REMOTE</a>, a single
+remote, 'origin', is normally used as the reference.  This one remote is
+considered canonical; even if you use multiple remotes, you probably want to
+retain your local copies until they've made it to that remote. 'origin' is used
+by default because that will usually be a main central repo, or your fork of
+it - in both cases that's a valid remote backup of your work. If origin doesn't
+exist then by default nothing will be pruned because everything is treated as
+'unpushed'.</p>
+
+<p>You can alter the remote via git config: <code>lfs.pruneremotetocheck</code>. Set this
+to a different remote name to check that one instead of 'origin'.</p>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><span class="man-ref">git-lfs-fetch<span class="s">(1)</span></span></p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-prune(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

man/git-lfs-pull.1

@@ -0,0 +1,47 @@
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
+.
+.TH "GIT\-LFS\-PULL" "1" "October 2021" "" ""
+.
+.SH "NAME"
+\fBgit\-lfs\-pull\fR \- Download all Git LFS files for current ref & checkout
+.
+.SH "SYNOPSIS"
+\fBgit lfs pull\fR [options] [\fIremote\fR]
+.
+.SH "DESCRIPTION"
+Download Git LFS objects for the currently checked out ref, and update the working copy with the downloaded content if required\.
+.
+.P
+This is equivalent to running the following 2 commands:
+.
+.P
+git lfs fetch [options] [\fIremote\fR] git lfs checkout
+.
+.SH "OPTIONS"
+.
+.TP
+\fB\-I\fR \fIpaths\fR \fB\-\-include=\fR\fIpaths\fR
+Specify lfs\.fetchinclude just for this invocation; see [INCLUSION & EXCLUSION]
+.
+.TP
+\fB\-X\fR \fIpaths\fR \fB\-\-exclude=\fR\fIpaths\fR
+Specify lfs\.fetchexclude just for this invocation; see [INCLUSION & EXCLUSION]
+.
+.SH "INCLUSION & EXCLUSION"
+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\.
+.
+.P
+In gitconfig, set lfs\.fetchinclude and lfs\.fetchexclude to comma\-separated lists of paths to include/exclude in the fetch (wildcard matching as per gitignore)\. Only paths which are matched by fetchinclude and not matched by fetchexclude will have objects fetched for them\.
+.
+.P
+Note that using the command\-line options \fB\-I\fR and \fB\-X\fR override the respective configuration settings\. Setting either option to an empty string clears the value\.
+.
+.SH "DEFAULT REMOTE"
+Without arguments, pull downloads from the default remote\. The default remote is the same as for \fBgit pull\fR, i\.e\. based on the remote branch you\'re tracking first, or origin otherwise\.
+.
+.SH "SEE ALSO"
+git\-lfs\-fetch(1), git\-lfs\-checkout(1)\.
+.
+.P
+Part of the git\-lfs(1) suite\.

man/git-lfs-pull.1.html

@@ -0,0 +1,134 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' value='text/html;charset=utf8'>
+  <meta name='generator' value='Ronn/v0.7.3 (http://github.com/rtomayko/ronn/tree/0.7.3)'>
+  <title>git-lfs-pull(1) - Download all Git LFS files for current ref &amp;amp; checkout</title>
+  <style type='text/css' media='all'>
+  /* style: man */
+  body#manpage {margin:0}
+  .mp {max-width:100ex;padding:0 9ex 1ex 4ex}
+  .mp p,.mp pre,.mp ul,.mp ol,.mp dl {margin:0 0 20px 0}
+  .mp h2 {margin:10px 0 0 0}
+  .mp > p,.mp > pre,.mp > ul,.mp > ol,.mp > dl {margin-left:8ex}
+  .mp h3 {margin:0 0 0 4ex}
+  .mp dt {margin:0;clear:left}
+  .mp dt.flush {float:left;width:8ex}
+  .mp dd {margin:0 0 0 9ex}
+  .mp h1,.mp h2,.mp h3,.mp h4 {clear:left}
+  .mp pre {margin-bottom:20px}
+  .mp pre+h2,.mp pre+h3 {margin-top:22px}
+  .mp h2+pre,.mp h3+pre {margin-top:5px}
+  .mp img {display:block;margin:auto}
+  .mp h1.man-title {display:none}
+  .mp,.mp code,.mp pre,.mp tt,.mp kbd,.mp samp,.mp h3,.mp h4 {font-family:monospace;font-size:14px;line-height:1.42857142857143}
+  .mp h2 {font-size:16px;line-height:1.25}
+  .mp h1 {font-size:20px;line-height:2}
+  .mp {text-align:justify;background:#fff}
+  .mp,.mp code,.mp pre,.mp pre code,.mp tt,.mp kbd,.mp samp {color:#131211}
+  .mp h1,.mp h2,.mp h3,.mp h4 {color:#030201}
+  .mp u {text-decoration:underline}
+  .mp code,.mp strong,.mp b {font-weight:bold;color:#131211}
+  .mp em,.mp var {font-style:italic;color:#232221;text-decoration:none}
+  .mp a,.mp a:link,.mp a:hover,.mp a code,.mp a pre,.mp a tt,.mp a kbd,.mp a samp {color:#0000ff}
+  .mp b.man-ref {font-weight:normal;color:#434241}
+  .mp pre {padding:0 4ex}
+  .mp pre code {font-weight:normal;color:#434241}
+  .mp h2+pre,h3+pre {padding-left:0}
+  ol.man-decor,ol.man-decor li {margin:3px 0 10px 0;padding:0;float:left;width:33%;list-style-type:none;text-transform:uppercase;color:#999;letter-spacing:1px}
+  ol.man-decor {width:100%}
+  ol.man-decor li.tl {text-align:left}
+  ol.man-decor li.tc {text-align:center;letter-spacing:4px}
+  ol.man-decor li.tr {text-align:right;float:right}
+  </style>
+</head>
+<!--
+  The following styles are deprecated and will be removed at some point:
+  div#man, div#man ol.man, div#man ol.head, div#man ol.man.
+
+  The .man-page, .man-decor, .man-head, .man-foot, .man-title, and
+  .man-navigation should be used instead.
+-->
+<body id='manpage'>
+  <div class='mp' id='man'>
+
+  <div class='man-navigation' style='display:none'>
+    <a href="#NAME">NAME</a>
+    <a href="#SYNOPSIS">SYNOPSIS</a>
+    <a href="#DESCRIPTION">DESCRIPTION</a>
+    <a href="#OPTIONS">OPTIONS</a>
+    <a href="#INCLUSION-EXCLUSION">INCLUSION &amp; EXCLUSION</a>
+    <a href="#DEFAULT-REMOTE">DEFAULT REMOTE</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-pull(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-pull(1)</li>
+  </ol>
+
+  <h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-pull</code> - <span class="man-whatis">Download all Git LFS files for current ref &amp; checkout</span>
+</p>
+
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs pull</code> [options] [<var>remote</var>]</p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Download Git LFS objects for the currently checked out ref, and update
+the working copy with the downloaded content if required.</p>
+
+<p>This is equivalent to running the following 2 commands:</p>
+
+<p>git lfs fetch [options] [<var>remote</var>]
+git lfs checkout</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<dl>
+<dt><code>-I</code> <var>paths</var> <code>--include=</code><var>paths</var></dt><dd><p>Specify lfs.fetchinclude just for this invocation; see [INCLUSION &amp; EXCLUSION]</p></dd>
+<dt><code>-X</code> <var>paths</var> <code>--exclude=</code><var>paths</var></dt><dd><p>Specify lfs.fetchexclude just for this invocation; see [INCLUSION &amp; EXCLUSION]</p></dd>
+</dl>
+
+
+<h2 id="INCLUSION-EXCLUSION">INCLUSION &amp; EXCLUSION</h2>
+
+<p>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.</p>
+
+<p>In gitconfig, set lfs.fetchinclude and lfs.fetchexclude to comma-separated lists
+of paths to include/exclude in the fetch (wildcard matching as per gitignore).
+Only paths which are matched by fetchinclude and not matched by fetchexclude
+will have objects fetched for them.</p>
+
+<p>Note that using the command-line options <code>-I</code> and <code>-X</code> override the respective
+configuration settings.  Setting either option to an empty string clears the
+value.</p>
+
+<h2 id="DEFAULT-REMOTE">DEFAULT REMOTE</h2>
+
+<p>Without arguments, pull downloads from the default remote. The default remote is
+the same as for <code>git pull</code>, i.e. based on the remote branch you're tracking
+first, or origin otherwise.</p>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><span class="man-ref">git-lfs-fetch<span class="s">(1)</span></span>, <span class="man-ref">git-lfs-checkout<span class="s">(1)</span></span>.</p>
+
+<p>Part of the <span class="man-ref">git-lfs<span class="s">(1)</span></span> suite.</p>
+
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>October 2021</li>
+    <li class='tr'>git-lfs-pull(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>