Upload folder using huggingface_hub

.gitattributes

@@ -33,3 +33,4 @@ saved_model/**/* filter=lfs diff=lfs merge=lfs -text
 *.zip filter=lfs diff=lfs merge=lfs -text
 *.zst filter=lfs diff=lfs merge=lfs -text
 *tfevents* filter=lfs diff=lfs merge=lfs -text
+git-lfs-3.2.0/git-lfs filter=lfs diff=lfs merge=lfs -text

config.json

@@ -0,0 +1,26 @@
+{
+  "_name_or_path": "mistralai/Mistral-7B-Instruct-v0.2",
+  "architectures": [
+    "MistralForCausalLM"
+  ],
+  "attention_dropout": 0.0,
+  "bos_token_id": 1,
+  "eos_token_id": 2,
+  "hidden_act": "silu",
+  "hidden_size": 4096,
+  "initializer_range": 0.02,
+  "intermediate_size": 14336,
+  "max_position_embeddings": 32768,
+  "model_type": "mistral",
+  "num_attention_heads": 32,
+  "num_hidden_layers": 32,
+  "num_key_value_heads": 8,
+  "rms_norm_eps": 1e-05,
+  "rope_theta": 1000000.0,
+  "sliding_window": null,
+  "tie_word_embeddings": false,
+  "torch_dtype": "bfloat16",
+  "transformers_version": "4.40.0.dev0",
+  "use_cache": false,
+  "vocab_size": 32000
+}

generation_config.json

@@ -0,0 +1,7 @@
+{
+  "_from_model_config": true,
+  "bos_token_id": 1,
+  "do_sample": true,
+  "eos_token_id": 2,
+  "transformers_version": "4.40.0.dev0"
+}

git-lfs-3.2.0/README.md

@@ -0,0 +1,259 @@
+# 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).
+
+Note that Debian and RPM packages are built for all OSes for amd64 and i386.
+For arm64, only Debian packages for the latest Debian release are built due to the cost of building in emulation.
+
+### 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 install github.com/josephspurrier/goversioninfo/cmd/goversioninfo@latest`.
+- 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
+```
+
+For the convenience of distributors, we also provide a wider variety of signed
+hashes in the `hashes.asc` file.  Those hashes are in the tagged BSD format, but
+can be verified with Perl's `shasum` or the GNU hash utilities, just like the
+ones in `sha256sums.asc`.
+
+## 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
+> ```
+>
+> **Note that this will rewrite history and change all of the Git object IDs in your
+> repository, just like the export version of this command.**
+>
+> 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-3.2.0/git-lfs

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:05309d4bc952e77251de76d8dda6bfbb9e9f532757abfc41a454f0e8327d7e33
+size 10768384

git-lfs-3.2.0/install.sh

@@ -0,0 +1,22 @@
+#!/usr/bin/env bash
+set -eu
+
+prefix="/usr/local"
+
+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

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

@@ -0,0 +1,178 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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>glob-pattern</var>...]<br>
+<code>git lfs checkout</code> --to <var>file</var> {--base|--ours|--theirs} <var>conflict-obj-path</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 <a class="man-ref" href="git-lfs-fetch.1.html">git-lfs-fetch<span class="s">(1)</span></a> 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>One or more <var>glob-pattern</var>s may be provided as arguments to restrict the
+set of files that are updated. Glob patterns are matched as per the format
+described in <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.</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 a conflicting Git LFS
+object into a separate file (which can be outside of the work tree).
+This can make using diff tools to inspect and resolve merges easier.
+A single Git LFS object's file path must be provided in <var>conflict-obj-path</var>.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<dl>
+<dt><code>--base</code></dt>
+<dd>Check out the merge base of the specified file.</dd>
+<dt><code>--ours</code></dt>
+<dd>Check out our side (that of the current branch) of the conflict for the
+specified file.</dd>
+<dt><code>--theirs</code></dt>
+<dd>Check out their side (that of the other branch) of the conflict for the
+specified file.</dd>
+<dt>
+<code>--to</code> <var>path</var>
+</dt>
+<dd>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.</dd>
+</dl>
+
+<h2 id="EXAMPLES">EXAMPLES</h2>
+
+<dl>
+<dt>Checkout all files that are missing or placeholders:</dt>
+<dd></dd>
+</dl>
+
+<p><code>
+$ git lfs checkout
+</code></p>
+
+<dl>
+<dt>Checkout a specific couple of files:</dt>
+<dd></dd>
+</dl>
+
+<p><code>
+$ git lfs checkout path/to/file1.png path/to.file2.png
+</code></p>
+
+<dl>
+<dt>Checkout a path with a merge conflict into separate files:</dt>
+<dd></dd>
+</dl>
+
+<p>```
+# Attempt merge with a branch that has a merge conflict
+$ git merge conflicting-branch
+CONFLICT (content): Merge conflict in path/to/conflicting/file.dat</p>
+
+<h1 id="Checkout-versions-of-the-conflicting-file-into-temp-files">Checkout versions of the conflicting file into temp files</h1>
+<p>$ git lfs checkout ours.dat --ours path/to/conflicting/file.dat
+$ git lfs checkout theirs.dat --theirs path/to/conflicting/file.dat</p>
+
+<h1 id="Compare-conflicting-versions-in-ours-dat-and-theirs-dat-">Compare conflicting versions in ours.dat and theirs.dat,</h1>
+<p># then resolve conflict (e.g., by choosing one version over
+# the other, or creating a new version)</p>
+
+<h1 id="Cleanup-and-continue-with-merge">Cleanup and continue with merge</h1>
+<p>$ rm ours.dat theirs.dat
+$ git add path/to/conflicting/file.dat
+$ git merge --continue
+```</p>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><a class="man-ref" href="git-lfs-fetch.1.html">git-lfs-fetch<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-pull.1.html">git-lfs-pull<span class="s">(1)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-checkout(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-clean.1.html

@@ -0,0 +1,104 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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 <a class="man-ref" href="git-lfs-pointer.1.html">git-lfs-pointer<span class="s">(1)</span></a>
+command.</p>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><a class="man-ref" href="git-lfs-install.1.html">git-lfs-install<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-push.1.html">git-lfs-push<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-pointer.1.html">git-lfs-pointer<span class="s">(1)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitattributes">gitattributes<span class="s">(5)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-clean(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-clone.1.html

@@ -0,0 +1,145 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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>See <a href="#INCLUDE-AND-EXCLUDE" title="INCLUDE AND EXCLUDE" data-bare-link="true">INCLUDE AND EXCLUDE</a>
+</dd>
+<dt>
+<code>-X</code> <var>paths</var> <code>--exclude=</code><var>paths</var>
+</dt>
+<dd>See <a href="#INCLUDE-AND-EXCLUDE" title="INCLUDE AND EXCLUDE" data-bare-link="true">INCLUDE AND EXCLUDE</a>
+</dd>
+<dt><code>--skip-repo</code></dt>
+<dd>Skip installing repo-level hooks (.git/hooks) that LFS requires. Disabled by
+default.</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 your Git configuration or in a <code>.lfsconfig</code> file, you may set either or
+both of <code>lfs.fetchinclude</code> and <code>lfs.fetchexclude</code> to comma-separated lists of
+paths.  If <code>lfs.fetchinclude</code> is defined, Git LFS objects will only be fetched
+if their path matches one in that list, and if <code>lfs.fetchexclude</code> is defined,
+Git LFS objects will only be fetched if their path does not match one
+in that list.  Paths are matched using wildcard matching as per <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.</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="SEE-ALSO">SEE ALSO</h2>
+
+<p><a class="man-ref" href="https://git-scm.com/docs/git-clone">git-clone<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-pull.1.html">git-lfs-pull<span class="s">(1)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-clone(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-config.5.html

@@ -0,0 +1,604 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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&gt;.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&gt;.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&gt;.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) with a Git for Windows version less than
+2.34.0 due to a limitation in Git.  Default: true if the version is less than
+2.34.0, false otherwise.</p>
+  </li>
+</ul>
+
+<h3 id="Upload-and-download-transfer-settings">Upload and download transfer 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&gt;</code> settings group.</p>
+  </li>
+  <li>
+    <p><code>lfs.customtransfer.&lt;name&gt;.path</code></p>
+
+    <p><code>lfs.customtransfer.&lt;name&gt;</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&gt;.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&gt;.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&gt;.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
+<a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>. See <a class="man-ref" href="git-lfs-fetch.1.html">git-lfs-fetch<span class="s">(1)</span></a> 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
+<a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>. See <a class="man-ref" href="git-lfs-fetch.1.html">git-lfs-fetch<span class="s">(1)</span></a> 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&gt;.&lt;setting&gt;</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:
+* <code>clean</code> The command which runs when files are added to the index
+* <code>smudge</code> The command which runs when files are written to the working copy
+* <code>priority</code> The order of this extension compared to others</p>
+  </li>
+</ul>
+
+<h3 id="Other-settings">Other settings</h3>
+
+<ul>
+  <li>
+    <p><code>lfs.&lt;url&gt;.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&gt;.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&gt;.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&gt; &lt;current&gt;/&lt;total files&gt; &lt;downloaded&gt;/&lt;total&gt; &lt;name&gt;</code></p>
+
+    <p>Each field is described below:
+* <code>direction</code>: The direction of transfer, either "checkout", "download", or
+  "upload".
+* <code>current</code> The index of the currently transferring file.
+* <code>total files</code> The estimated count of all files to be transferred.
+* <code>downloaded</code> The number of bytes already downloaded.
+* <code>total</code> The entire size of the file, in bytes.
+* <code>name</code> The name of the file.</p>
+  </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><a class="man-ref" href="https://git-scm.com/docs/git-config">git-config<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-install.1.html">git-lfs-install<span class="s">(1)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitattributes">gitattributes<span class="s">(5)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-config(5)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-dedup.1.html

@@ -0,0 +1,102 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <title>git-lfs-dedup(1) - Deduplicate Git LFS files</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-dedup(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-dedup(1)</li>
+  </ol>
+
+  
+
+<h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-dedup</code> - <span class="man-whatis">Deduplicate Git LFS files</span>
+</p>
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs dedup</code></p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Deduplicates storage by re-creating working tree files as clones of the files in the Git LFS storage directory
+using the operating system's copy-on-write file creation functionality.</p>
+
+<p>If the operating system or file system don't support copy-on-write file creation, this command exits unsuccessfully.</p>
+
+<p>This command will also exit without success if any Git LFS extensions are
+configured, as these will typically be used to alter the file contents
+before they are written to the Git LFS storage directory, and therefore the
+working tree files should not be copy-on-write clones of the LFS object files.</p>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-dedup(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-env.1.html

@@ -0,0 +1,94 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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 <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-env(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-ext.1.html

@@ -0,0 +1,112 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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 <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-ext(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-fetch.1.html

@@ -0,0 +1,268 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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>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>
+</dd>
+<dt>
+<code>-X</code> <var>paths</var> <code>--exclude=</code><var>paths</var>
+</dt>
+<dd>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>
+</dd>
+<dt><code>--recent</code></dt>
+<dd>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>
+</dd>
+<dt><code>--all</code></dt>
+<dd>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.</dd>
+<dt>
+<code>--prune</code> <code>-p</code>
+</dt>
+<dd>Prune old and unreferenced objects after fetching, equivalent to running
+<code>git lfs prune</code> afterwards. See <a class="man-ref" href="git-lfs-prune.1.html">git-lfs-prune<span class="s">(1)</span></a> for more details.</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 your Git configuration or in a <code>.lfsconfig</code> file, you may set either or
+both of <code>lfs.fetchinclude</code> and <code>lfs.fetchexclude</code> to comma-separated lists of
+paths.  If <code>lfs.fetchinclude</code> is defined, Git LFS objects will only be fetched
+if their path matches one in that list, and if <code>lfs.fetchexclude</code> is defined,
+Git LFS objects will only be fetched if their path does not match one
+in that list.  Paths are matched using wildcard matching as per <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.</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><a class="man-ref" href="git-lfs-checkout.1.html">git-lfs-checkout<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-pull.1.html">git-lfs-pull<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-prune.1.html">git-lfs-prune<span class="s">(1)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitconfig">gitconfig<span class="s">(5)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-fetch(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

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

@@ -0,0 +1,127 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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>In your Git configuration or in a <code>.lfsconfig</code> file, you may set either or
+both of <code>lfs.fetchinclude</code> and <code>lfs.fetchexclude</code> to comma-separated lists of
+paths.  If <code>lfs.fetchinclude</code> is defined, Git LFS pointer files will only be
+replaced with the contents of the corresponding Git LFS object file if their
+path matches one in that list, and if <code>lfs.fetchexclude</code> is defined, Git LFS
+pointer files will only be replaced with the contents of the corresponding
+Git LFS object file if their path does not match one in that list.  Paths are
+matched using wildcard matching as per <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.  Git LFS pointer files
+that are not replaced with the contents of their corresponding object files
+are simply copied to standard output without change.</p>
+
+<p>The filter process uses Git's pkt-line protocol to communicate, and is
+documented in detail in <a class="man-ref" href="https://git-scm.com/docs/gitattributes">gitattributes<span class="s">(5)</span></a>.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<p>Without any options, filter-process accepts and responds to requests normally.</p>
+
+<dl>
+<dt><code>--skip</code></dt>
+<dd>  Skip automatic downloading of objects on clone or pull.</dd>
+<dt><code>GIT_LFS_SKIP_SMUDGE</code></dt>
+<dd>  Disables the smudging process. For more, see: <a class="man-ref" href="git-lfs-config.5.html">git-lfs-config<span class="s">(5)</span></a>.</dd>
+</dl>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><a class="man-ref" href="git-lfs-clean.1.html">git-lfs-clean<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-install.1.html">git-lfs-install<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-smudge.1.html">git-lfs-smudge<span class="s">(1)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitattributes">gitattributes<span class="s">(5)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-filter-process(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-fsck.1.html

@@ -0,0 +1,123 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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>
+
+<p>In your Git configuration or in a <code>.lfsconfig</code> file, you may set
+<code>lfs.fetchexclude</code> to a comma-separated list of paths.  If <code>lfs.fetchexclude</code>
+is defined, then any Git LFS files whose paths match one in that list will
+not be checked for consistency.  Paths are matched using wildcard matching as
+per <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.</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><a class="man-ref" href="git-lfs-ls-files.1.html">git-lfs-ls-files<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-status.1.html">git-lfs-status<span class="s">(1)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-fsck(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-install.1.html

@@ -0,0 +1,143 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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 <a class="man-ref" href="git-lfs-pre-push.1.html">git-lfs-pre-push<span class="s">(1)</span></a> 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><code>--force</code></dt>
+<dd>  Sets the "lfs" smudge and clean filters, overwriting existing values.</dd>
+<dt><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><a class="man-ref" href="git-lfs-uninstall.1.html">git-lfs-uninstall<span class="s">(1)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/git-worktree">git-worktree<span class="s">(1)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-install(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-lock.1.html

@@ -0,0 +1,116 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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&gt;.locksverify</code> config key in
+<a class="man-ref" href="git-lfs-config.5.html">git-lfs-config<span class="s">(5)</span></a> for details.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<dl>
+<dt>
+<code>-r</code> <var>name</var> <code>--remote=</code><var>name</var>
+</dt>
+<dd>Specify the Git LFS server to use. Ignored if the <code>lfs.url</code> config key is set.</dd>
+<dt><code>--json</code></dt>
+<dd>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.</dd>
+</dl>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><a class="man-ref" href="git-lfs-unlock.1.html">git-lfs-unlock<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-locks.1.html">git-lfs-locks<span class="s">(1)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-lock(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-locks.1.html

@@ -0,0 +1,138 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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>Specify the Git LFS server to use. Ignored if the <code>lfs.url</code> config key is set.</dd>
+<dt>
+<code>-i &lt;id&gt;</code> <code>--id=&lt;id&gt;</code>
+</dt>
+<dd>Specifies a lock by its ID. Returns a single result.</dd>
+<dt>
+<code>-p &lt;path&gt;</code> <code>--path=&lt;path&gt;</code>
+</dt>
+<dd>Specifies a lock by its path. Returns a single result.</dd>
+<dt><code>--local</code></dt>
+<dd>Lists only our own locks which are cached locally. Skips a remote call.</dd>
+<dt><code>--cached</code></dt>
+<dd>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.</dd>
+<dt><code>--verify</code></dt>
+<dd>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).</dd>
+<dt>
+<code>-l &lt;num&gt;</code> <code>--limit=&lt;num&gt;</code>
+</dt>
+<dd>Specifies number of results to return.</dd>
+<dt><code>--json</code></dt>
+<dd>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.</dd>
+</dl>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><a class="man-ref" href="git-lfs-lock.1.html">git-lfs-lock<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-unlock.1.html">git-lfs-unlock<span class="s">(1)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-locks(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-logs.1.html

@@ -0,0 +1,118 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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><code>clear</code></dt>
+<dd>  Clears all of the existing logged errors.</dd>
+<dt><code>boomtown</code></dt>
+<dd>  Triggers a dummy exception.</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><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 <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-logs(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

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

@@ -0,0 +1,141 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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>
+  </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>Show the entire 64 character OID, instead of just first 10.</dd>
+<dt>
+<code>-s</code> <code>--size</code>
+</dt>
+<dd>Show the size of the LFS object between parenthesis at the end of a line.</dd>
+<dt>
+<code>-d</code> <code>--debug</code>
+</dt>
+<dd>Show as much information as possible about a LFS file. This is intended
+for manual inspection; the exact format may change at any time.</dd>
+<dt>
+<code>-a</code> <code>--all</code>
+</dt>
+<dd>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.</dd>
+<dt><code>--deleted</code></dt>
+<dd>Shows the full history of the given reference, including objects that have
+been deleted.</dd>
+<dt>
+<code>-I</code> <var>paths</var> <code>--include=</code><var>paths</var>
+</dt>
+<dd>Include paths matching only these patterns; see [FETCH SETTINGS].</dd>
+<dt>
+<code>-X</code> <var>paths</var> <code>--exclude=</code><var>paths</var>
+</dt>
+<dd>Exclude paths matching any of these patterns; see [FETCH SETTINGS].</dd>
+<dt>
+<code>-n</code> <code>--name-only</code>
+</dt>
+<dd>Show only the lfs tracked file names.
+## SEE ALSO</dd>
+</dl>
+
+<p><a class="man-ref" href="git-lfs-status.1.html">git-lfs-status<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-config.5.html">git-lfs-config<span class="s">(5)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-ls-files(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-merge-driver.1.html

@@ -0,0 +1,188 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <title>git-lfs-merge-driver(1) - Merge text-based LFS files</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="#CONFIGURATION">CONFIGURATION</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-merge-driver(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-merge-driver(1)</li>
+  </ol>
+
+  
+
+<h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-merge-driver</code> - <span class="man-whatis">Merge text-based LFS files</span>
+</p>
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs merge-driver</code> <a href="#OPTIONS" title="OPTIONS" data-bare-link="true">options</a></p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Merge text files stored in Git LFS using the default Git merge machinery, or a
+custom merge driver if specified.  Note that this, in general, does not support
+partial renames or copies because Git does not support them in this case.</p>
+
+<p>This program is intended to be invoked automatically by Git and not by users
+manually.  See <a href="#CONFIGURATION" title="CONFIGURATION" data-bare-link="true">CONFIGURATION</a> for details on the configuration required for
+that.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<ul>
+  <li>
+    <p><code>--ancestor</code> <var>path</var>
+Specify the file containing the ancestor revision.</p>
+  </li>
+  <li>
+    <p><code>--current</code> <var>path</var>
+Specify the file containing the current revision.</p>
+  </li>
+  <li>
+    <p><code>--marker-size</code> <var>num</var>
+Specify the conflict marker size as an integer.</p>
+  </li>
+  <li>
+    <p><code>--other</code> <var>path</var>
+Specify the file containing the other revision.</p>
+  </li>
+  <li>
+    <p><code>--program</code> <var>program</var>
+Specify a command, which is passed to the shell after substitution, that
+performs the actual merge.  If this is not specified, <code>git merge-file</code> is
+invoked with appropriate arguments to perform the merge of the file.</p>
+
+    <p>See <a href="#CONFIGURATION" title="CONFIGURATION" data-bare-link="true">CONFIGURATION</a> for the sequences which are substituted here.</p>
+  </li>
+</ul>
+
+<h2 id="CONFIGURATION">CONFIGURATION</h2>
+
+<p>Git allows the use of a custom merge driver for files based on the <code>merge</code>
+attribute set in <code>.gitattributes</code>.  By default, when using <code>git lfs track</code>, this
+value is set to <code>lfs</code>.</p>
+
+<p>Because Git LFS can be used to store both text and binary files and it isn't
+always clear which behavior should be used, Git LFS does not enable this merge
+driver by default.  However, if you know that some or all of your files are text
+files, then you can set the <code>merge</code> attribute for those files to <code>lfs-text</code> and
+use <code>git config</code> to set the merge driver like so:</p>
+
+<p><code>console
+$ git config merge.lfs-text.driver 'git lfs merge-driver --ancestor %O --current %A --other %B --marker-size %L --output %A'
+</code></p>
+
+<p>This tells Git to invoke the custom Git LFS merge driver, which in turn uses
+Git's merge machinery, to merge files where the <code>merge</code> attribute is set to
+<code>lfs-text</code>.  Note that <code>lfs-text</code> here is an example and any syntactically valid
+value can be used.</p>
+
+<p>If you are using a special type of file that needs rules different from Git's
+standard merge machinery, you can also specify the <code>--program</code> option, which
+is passed to <code>sh</code> after substituting its own percent-encoded escapes:</p>
+
+<ul>
+  <li>
+<code>%A</code>: the current version</li>
+  <li>
+<code>%B</code>: the other version</li>
+  <li>
+<code>%D</code>: the destination version</li>
+  <li>
+<code>%O</code>: the ancestor version</li>
+  <li>
+<code>%L</code>: the conflict marker size</li>
+</ul>
+
+<p>Note that the percent sign must typically be doubled to prevent Git from
+substituting its own values here.  Therefore, specifying the default behavior
+explicitly looks like this:</p>
+
+<p><code>console
+$ git config merge.lfs-text.driver \
+  'git lfs merge-driver --ancestor %O --current %A --other %B --marker-size %L --output %A --program '\''git merge-file --stdout --marker-size=%%L %%A %%O %%B &gt;%%D'\'''
+</code></p>
+
+<p>The exit status from the custom command should be zero on success or non-zero on
+conflicts or other failure.</p>
+
+<p>Note that if no merge driver is specified for the value of the <code>merge</code> attribute
+(as is the case by default with <code>merge=lfs</code>), then the default Git merge
+strategy is used.  For LFS files, this means that Git will try to merge the
+pointer files, which usually is not useful.</p>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><a class="man-ref" href="https://git-scm.com/docs/git-merge">git-merge<span class="s">(1)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/git-merge-file">git-merge-file<span class="s">(1)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitattributes">gitattributes<span class="s">(5)</span></a></p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-merge-driver(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-migrate.1.html

@@ -0,0 +1,590 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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-REFERENCES">INCLUDE AND EXCLUDE REFERENCES</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 <a href="#IMPORT-WITHOUT-REWRITING-HISTORY" title="IMPORT WITHOUT REWRITING HISTORY" data-bare-link="true">IMPORT WITHOUT REWRITING HISTORY</a>
+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 <a href="#INCLUDE-AND-EXCLUDE-REFERENCES" title="INCLUDE AND EXCLUDE REFERENCES" data-bare-link="true">INCLUDE AND EXCLUDE REFERENCES</a> 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.  The <code>.gitattributes</code> files will always be assigned the default
+read/write permissions mode (i.e., without execute permissions).  Any
+symbolic links with that name will cause the migration to halt prematurely.</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
+  <a href="#IMPORT-WITHOUT-REWRITING-HISTORY" title="IMPORT WITHOUT REWRITING HISTORY" data-bare-link="true">IMPORT WITHOUT REWRITING HISTORY</a>.</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>  See <a href="#INCLUDE-AND-EXCLUDE" title="INCLUDE AND EXCLUDE" data-bare-link="true">INCLUDE AND EXCLUDE</a>.</dd>
+<dt>
+<code>-X</code> <var>paths</var> <code>--exclude=</code><var>paths</var>
+</dt>
+<dd>  See <a href="#INCLUDE-AND-EXCLUDE" title="INCLUDE AND EXCLUDE" data-bare-link="true">INCLUDE AND EXCLUDE</a>.</dd>
+<dt>
+<code>--include-ref</code>=<var>refname</var>
+</dt>
+<dd>  See <a href="#INCLUDE-AND-EXCLUDE-REFERENCES" title="INCLUDE AND EXCLUDE REFERENCES" data-bare-link="true">INCLUDE AND EXCLUDE REFERENCES</a>.</dd>
+<dt>
+<code>--exclude-ref</code>=<var>refname</var>
+</dt>
+<dd>  See <a href="#INCLUDE-AND-EXCLUDE-REFERENCES" title="INCLUDE AND EXCLUDE REFERENCES" data-bare-link="true">INCLUDE AND EXCLUDE REFERENCES</a>.</dd>
+<dt><code>--skip-fetch</code></dt>
+<dd>  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>.</dd>
+<dt><code>--everything</code></dt>
+<dd>  See <a href="#INCLUDE-AND-EXCLUDE-REFERENCES" title="INCLUDE AND EXCLUDE REFERENCES" data-bare-link="true">INCLUDE AND EXCLUDE REFERENCES</a>.
+
+    <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><code>--yes</code></dt>
+<dd>  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.</dd>
+<dt>[branch ...]</dt>
+<dd>  Migrate only the set of branches listed. If not given, <code>git-lfs-migrate(1)</code>
+  will migrate the currently checked out branch.
+
+    <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&gt;</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&gt;</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&gt;</code>
+  Format the number of bytes in each entry as a quantity of the storage unit
+  provided. Valid units include:
+    * b, kib, mib, gib, tib, pib - for IEC storage units
+    * b, kb, mb, gb, tb, pb - for SI storage units</p>
+
+    <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
+  <code>.gitattributes</code> files in a repository. In practice, this option counts any
+  filepaths which should be tracked by Git LFS according to the repository's
+  <code>.gitattributes</code> file(s), but aren't already pointers. The <code>.gitattributes</code>
+  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>
+
+<p><code>
+*.gif             	93 MB 	9480/10504 files(s)	 90%
+*.png              	14 MB 	 1732/1877 files(s)	 92%
+</code></p>
+
+<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&gt;</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.  This option cannot be used with
+  the <code>--include</code>, <code>--exclude</code>, and <code>--fixup</code> options.</p>
+  </li>
+  <li>
+    <p><code>--object-map=&lt;path&gt;</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
+  <a href="#IMPORT-WITHOUT-REWRITING-HISTORY" title="IMPORT WITHOUT REWRITING HISTORY" data-bare-link="true">IMPORT WITHOUT REWRITING HISTORY</a>.</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-WITHOUT-REWRITING-HISTORY">IMPORT WITHOUT REWRITING HISTORY</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&gt; --message=&lt;message&gt;</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&gt;</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&gt;</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>
+
+<p>Note that this form of pattern matching for the <code>--include</code> and <code>--exclude</code>
+options used by the <code>git lfs migrate</code> command is unique among the suite of
+<code>git lfs</code> commands.  Other commands which also take these options, such as
+<code>git lfs ls-files</code>, use the <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a> form of pattern matching instead.</p>
+
+<h2 id="INCLUDE-AND-EXCLUDE-REFERENCES">INCLUDE AND EXCLUDE REFERENCES</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>
+
+<p><code>
+        D---E---F
+       /         \
+  A---B------C    refs/heads/my-feature
+   \          \
+    \          refs/heads/main
+     \
+      refs/remotes/origin/main
+</code></p>
+
+<p>In the above configuration, the following commits are reachable by each ref:</p>
+
+<p><code>
+refs/heads/main:           C, B, A
+refs/heads/my-feature:     F, E, D, B, A
+refs/remote/origin/main:   A
+</code></p>
+
+<p>The following <code>git lfs migrate</code> options would, therefore, include commits
+F, E, D, C, and B, but exclude commit A:</p>
+
+<p><code>
+  --include-ref=refs/heads/my-feature
+  --include-ref=refs/heads/main
+  --exclude-ref=refs/remotes/origin/main
+</code></p>
+
+<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>
+
+<p><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></p>
+
+<p>Now, you can run <code>git lfs migrate import</code> to convert some file types to LFS:</p>
+
+<p><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></p>
+
+<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>
+
+<p>```
+# Check for large files and existing Git LFS objects in your local main branch
+$ git lfs migrate info --include-ref=main</p>
+
+<h1 id="Check-for-large-files-and-existing-Git-LFS-objects-in-every-branch">Check for large files and existing Git LFS objects in every branch</h1>
+<p>$ git lfs migrate info --everything</p>
+
+<h1 id="Check-for-large-files-in-every-branch-ignoring-any-existing-Git-LFS-objects-">Check for large files in every branch, ignoring any existing Git LFS objects,</h1>
+<p># and listing the top 100 or fewer results
+$ git lfs migrate info --everything --pointers=ignore --top=100
+```</p>
+
+<p>The same flags will work in <code>import</code> mode:</p>
+
+<p>```
+# Convert all zip files in your main branch
+$ git lfs migrate import --include-ref=main --include="*.zip"</p>
+
+<h1 id="Convert-all-zip-files-in-every-local-branch">Convert all zip files in every local branch</h1>
+<p>$ git lfs migrate import --everything --include="*.zip"</p>
+
+<h1 id="Convert-all-files-over-100K-in-every-local-branch">Convert all files over 100K in every local branch</h1>
+<p>$ git lfs migrate import --everything --above=100Kb
+```</p>
+
+<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>
+
+<p><code>
+$ git lfs migrate import --no-rewrite test.zip *.mp3 *.psd
+</code></p>
+
+<p>With a specified commit message:</p>
+
+<p><code>
+$ git lfs migrate import --no-rewrite \
+  -m "Import test.zip, .mp3, .psd files in root of repo" \
+  test.zip *.mp3 *.psd
+</code></p>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><a class="man-ref" href="git-lfs-checkout.1.html">git-lfs-checkout<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-ls-files.1.html">git-lfs-ls-files<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-track.1.html">git-lfs-track<span class="s">(1)</span></a>,
+<a class="man-ref" href="git-lfs-untrack.1.html">git-lfs-untrack<span class="s">(1)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitattributes">gitattributes<span class="s">(5)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-migrate(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-pointer.1.html

@@ -0,0 +1,125 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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><code>--file</code></dt>
+<dd>  A local file to build the pointer from.</dd>
+<dt><code>--pointer</code></dt>
+<dd>  A local file including the contents of a pointer generated from another
+  implementation.  This is compared to the pointer generated from <code>--file</code>.</dd>
+<dt><code>--stdin</code></dt>
+<dd>  Reads the pointer from STDIN to compare with the pointer generated from
+  <code>--file</code>.</dd>
+<dt><code>--check</code></dt>
+<dd>  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.</dd>
+<dt>
+<code>--strict</code>:</dt>
+<dd></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 <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-pointer(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

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

@@ -0,0 +1,98 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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><a class="man-ref" href="git-lfs-track.1.html">git-lfs-track<span class="s">(1)</span></a></p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-post-checkout(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

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

@@ -0,0 +1,103 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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><a class="man-ref" href="git-lfs-post-merge.1.html">git-lfs-post-merge<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-track.1.html">git-lfs-track<span class="s">(1)</span></a></p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-post-commit(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

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

@@ -0,0 +1,98 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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><a class="man-ref" href="git-lfs-track.1.html">git-lfs-track<span class="s">(1)</span></a></p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-post-merge(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

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

@@ -0,0 +1,119 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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&gt; SP &lt;local-sha1&gt; SP &lt;remote-ref&gt; SP &lt;remote-sha1&gt; \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: <a class="man-ref" href="git-lfs-config.5.html">git-lfs-config<span class="s">(5)</span></a>.</dd>
+</dl>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><a class="man-ref" href="git-lfs-clean.1.html">git-lfs-clean<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-push.1.html">git-lfs-push<span class="s">(1)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-pre-push(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-prune.1.html

@@ -0,0 +1,245 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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 <a class="man-ref" href="https://git-scm.com/docs/git-worktree">git-worktree<span class="s">(1)</span></a>
+</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 <a class="man-ref" href="git-lfs-config.5.html">git-lfs-config<span class="s">(5)</span></a> for more
+details about <code>lfs.storage</code> option.</p>
+
+<p>In your Git configuration or in a <code>.lfsconfig</code> file, you may set
+<code>lfs.fetchexclude</code> to a comma-separated list of paths.  If <code>lfs.fetchexclude</code>
+is defined, then any Git LFS files whose paths match one in that list will
+be pruned unless they are referenced by a stash or an unpushed commit.
+Paths are matched using wildcard matching as per <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.</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 <a class="man-ref" href="git-lfs-fetch.1.html">git-lfs-fetch<span class="s">(1)</span></a> 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 <a class="man-ref" href="https://git-scm.com/docs/git-config">git-config<span class="s">(1)</span></a> 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 <a class="man-ref" href="git-lfs-fetch.1.html">git-lfs-fetch<span class="s">(1)</span></a> 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><a class="man-ref" href="git-lfs-fetch.1.html">git-lfs-fetch<span class="s">(1)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-prune(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-pull.1.html

@@ -0,0 +1,143 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <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="#INCLUDE-AND-EXCLUDE">INCLUDE AND EXCLUDE</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>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>
+</dd>
+<dt>
+<code>-X</code> <var>paths</var> <code>--exclude=</code><var>paths</var>
+</dt>
+<dd>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>
+</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 your Git configuration or in a <code>.lfsconfig</code> file, you may set either or
+both of <code>lfs.fetchinclude</code> and <code>lfs.fetchexclude</code> to comma-separated lists of
+paths.  If <code>lfs.fetchinclude</code> is defined, Git LFS objects will only be fetched
+if their path matches one in that list, and if <code>lfs.fetchexclude</code> is defined,
+Git LFS objects will only be fetched if their path does not match one
+in that list.  Paths are matched using wildcard matching as per <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.</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><a class="man-ref" href="git-lfs-fetch.1.html">git-lfs-fetch<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-checkout.1.html">git-lfs-checkout<span class="s">(1)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-pull(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

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

@@ -0,0 +1,120 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <title>git-lfs-push(1) - Push queued large files to the Git LFS endpoint</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-push(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-push(1)</li>
+  </ol>
+
+  
+
+<h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-push</code> - <span class="man-whatis">Push queued large files to the Git LFS endpoint</span>
+</p>
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs push</code> <a href="#OPTIONS" title="OPTIONS" data-bare-link="true">options</a> <var>remote</var> [<var>ref</var>...]<br>
+<code>git lfs push</code> <var>remote</var> [<var>ref</var>...]<br>
+<code>git lfs push</code> --object-id <var>remote</var> [<var>oid</var>...]</p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Upload Git LFS files to the configured endpoint for the current Git remote.  By
+default, it filters out objects that are already referenced by the local clone
+of the remote.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<dl>
+<dt><code>--dry-run</code></dt>
+<dd>  Print the files that would be pushed, without actually pushing them.</dd>
+<dt><code>--all</code></dt>
+<dd>  This pushes all objects to the remote that are referenced by any commit
+  reachable from the refs provided as arguments. If no refs are provided, then
+  all local refs are pushed.  Note that this behavior differs from that of
+  <a class="man-ref" href="git-lfs-fetch.1.html">git-lfs-fetch<span class="s">(1)</span></a> when its <code>--all</code> option is used; in that case, all refs
+  are fetched, including refs other than those under <code>refs/heads</code> and
+  <code>refs/tags</code>.  If you are migrating a repository with these commands, make
+  sure to run <code>git lfs push</code> for any additional remote refs that contain
+  Git LFS objects not reachable from your local refs.</dd>
+<dt><code>--object-id</code></dt>
+<dd>  This pushes only the object OIDs listed at the end of the command, separated
+  by spaces.</dd>
+</dl>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><a class="man-ref" href="git-lfs-fetch.1.html">git-lfs-fetch<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-pre-push.1.html">git-lfs-pre-push<span class="s">(1)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-push(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-smudge.1.html

@@ -0,0 +1,134 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <title>git-lfs-smudge(1) - Git smudge filter that converts pointer in blobs to the 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="#KNOWN-BUGS">KNOWN BUGS</a>
+    <a href="#SEE-ALSO">SEE ALSO</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs-smudge(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-smudge(1)</li>
+  </ol>
+
+  
+
+<h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-smudge</code> - <span class="man-whatis">Git smudge filter that converts pointer in blobs to the actual content</span>
+</p>
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs smudge</code> [<var>path</var>]
+<code>git lfs smudge</code> --skip [<var>path</var>]</p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Read a Git LFS pointer file from standard input and write the contents
+of the corresponding large file to standard output.  If needed,
+download the file's contents from the Git LFS endpoint.  The <var>path</var>
+argument, if provided, is only used for a progress bar.</p>
+
+<p>Smudge is typically run by Git's smudge filter, configured by the repository's
+Git attributes.</p>
+
+<p>In your Git configuration or in a <code>.lfsconfig</code> file, you may set either or
+both of <code>lfs.fetchinclude</code> and <code>lfs.fetchexclude</code> to comma-separated lists of
+paths.  If <code>lfs.fetchinclude</code> is defined, Git LFS pointer files will only be
+replaced with the contents of the corresponding Git LFS object file if their
+path matches one in that list, and if <code>lfs.fetchexclude</code> is defined, Git LFS
+pointer files will only be replaced with the contents of the corresponding
+Git LFS object file if their path does not match one in that list.  Paths are
+matched using wildcard matching as per <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.  Git LFS pointer files
+that are not replaced with the contents of their corresponding object files
+are simply copied to standard output without change.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<p>Without any options, <code>git lfs smudge</code> outputs the raw Git LFS content to
+standard output.</p>
+
+<dl>
+<dt><code>--skip</code></dt>
+<dd>  Skip automatic downloading of objects on clone or pull.</dd>
+<dt><code>GIT_LFS_SKIP_SMUDGE</code></dt>
+<dd>  Disables the smudging process. For more, see: <a class="man-ref" href="git-lfs-config.5.html">git-lfs-config<span class="s">(5)</span></a>.</dd>
+</dl>
+
+<h2 id="KNOWN-BUGS">KNOWN BUGS</h2>
+
+<p>On Windows, Git before 2.34.0 does not handle files in the working tree larger
+than 4 gigabytes.  Newer versions of Git, as well as Unix versions, are
+unaffected.</p>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><a class="man-ref" href="git-lfs-install.1.html">git-lfs-install<span class="s">(1)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitattributes">gitattributes<span class="s">(5)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-smudge(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-standalone-file.1.html

@@ -0,0 +1,102 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <title>git-lfs-standalone-file(1) - Standalone transfer adapter for file URLs</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-standalone-file(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-standalone-file(1)</li>
+  </ol>
+
+  
+
+<h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-standalone-file</code> - <span class="man-whatis">Standalone transfer adapter for file URLs</span>
+</p>
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs standalone-file</code></p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Provides a standalone transfer adapter for file URLs (local paths).</p>
+
+<p>By default, Git LFS requires the support of an HTTP server to implement the Git
+LFS protocol. However, this tool allows the use of URLs starting with <code>file:///</code>
+(that is, those representing local paths) in addition. Configuration is not
+necessary; Git LFS handles this internally.</p>
+
+<p>When invoked, this tool speaks JSON on input and output as a standalone transfer
+adapter. It is not intended for use by end users.</p>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-standalone-file(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-status.1.html

@@ -0,0 +1,123 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <title>git-lfs-status(1) - Show the status of Git LFS files in the 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-status(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-status(1)</li>
+  </ol>
+
+  
+
+<h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-status</code> - <span class="man-whatis">Show the status of Git LFS files in the working tree</span>
+</p>
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs status</code> [<var>options</var>]</p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Display paths of Git LFS objects that</p>
+
+<ul>
+  <li>
+    <p>have not been pushed to the Git LFS server.  These are large files
+that would be uploaded by <code>git push</code>.</p>
+  </li>
+  <li>
+    <p>have differences between the index file and the current HEAD commit.
+These are large files that would be committed by <code>git commit</code>.</p>
+  </li>
+  <li>
+    <p>have differences between the working tree and the index file.  These
+are files that could be staged using <code>git add</code>.</p>
+  </li>
+</ul>
+
+<p>This command must be run in a non-bare repository.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<dl>
+<dt><code>--porcelain</code></dt>
+<dd>  Give the output in an easy-to-parse format for scripts.</dd>
+<dt><code>--json</code></dt>
+<dd>  Give the output in a stable json format for scripts.</dd>
+</dl>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><a class="man-ref" href="git-lfs-ls-files.1.html">git-lfs-ls-files<span class="s">(1)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-status(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-track.1.html

@@ -0,0 +1,179 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <title>git-lfs-track(1) - View or add Git LFS paths to Git attributes</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-track(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-track(1)</li>
+  </ol>
+
+  
+
+<h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-track</code> - <span class="man-whatis">View or add Git LFS paths to Git attributes</span>
+</p>
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs track</code> [options] [<var>pattern</var>...]</p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Start tracking the given patterns(s) through Git LFS.  The <var>pattern</var> argument
+is written to .gitattributes. If no paths are provided, simply list the
+currently-tracked paths.</p>
+
+<p>The <a href="https://git-scm.com/docs/gitattributes">gitattributes documentation</a> states
+that patterns use the <a href="https://git-scm.com/docs/gitignore">gitignore pattern rules</a>
+to match paths. This means that patterns which contain asterisk (<code>*</code>), question
+mark (<code>?</code>), and the bracket characters (<code>[</code> and <code>]</code>) are treated specially; to
+disable this behavior and treat them literally instead, use <code>--filename</code> or
+escape the character with a backslash.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<ul>
+  <li>
+    <p><code>--verbose</code> <code>-v</code>:
+If enabled, have <code>git lfs track</code> log files which it will touch. Disabled by
+default.</p>
+  </li>
+  <li>
+    <p><code>--dry-run</code> <code>-d</code>:
+If enabled, have <code>git lfs track</code> log all actions it would normally take
+(adding entries to .gitattributes, touching files on disk, etc) without
+performing any mutative operations to the disk.</p>
+
+    <p><code>git lfs track --dry-run [files]</code> also implicitly mocks the behavior of
+passing the <code>--verbose</code>, and will log in greater detail what it is doing.</p>
+
+    <p>Disabled by default.</p>
+  </li>
+  <li>
+    <p><code>--filename</code>
+Treat the arguments as literal filenames, not as patterns. Any special glob
+characters in the filename will be escaped when writing the <code>.gitattributes</code>
+file.</p>
+  </li>
+  <li>
+    <p><code>--lockable</code> <code>-l</code>
+Make the paths 'lockable', meaning they should be locked to edit them, and
+will be made read-only in the working copy when not locked.</p>
+  </li>
+  <li>
+    <p><code>--not-lockable</code>
+Remove the lockable flag from the paths so they are no longer read-only unless
+locked.</p>
+  </li>
+  <li>
+    <p><code>--no-excluded</code>
+Do not list patterns that are excluded in the output; only list patterns that
+are tracked.</p>
+  </li>
+  <li>
+    <p><code>--no-modify-attrs</code>
+Makes matched entries stat-dirty so that Git can re-index files you wish to
+convert to LFS. Does not modify any <code>.gitattributes</code> file(s).</p>
+  </li>
+</ul>
+
+<h2 id="EXAMPLES">EXAMPLES</h2>
+
+<dl>
+<dt>List the patterns that Git LFS is currently tracking:
+
+    <p><code>git lfs track</code></p>
+</dt>
+<dd></dd>
+<dt>Configure Git LFS to track GIF files:
+
+    <p><code>git lfs track "*.gif"</code></p>
+</dt>
+<dd></dd>
+<dt>Configure Git LFS to track PSD files and make them read-only unless locked:
+
+    <p><code>git lfs track --lockable "*.psd"</code></p>
+</dt>
+<dd></dd>
+<dt>Configure Git LFS to track the file named <code>project [1].psd</code>:
+
+    <p><code>git lfs track --filename "project [1].psd"</code></p>
+</dt>
+<dd></dd>
+</dl>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><a class="man-ref" href="git-lfs-untrack.1.html">git-lfs-untrack<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-install.1.html">git-lfs-install<span class="s">(1)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitattributes">gitattributes<span class="s">(5)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitignore">gitignore<span class="s">(5)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-track(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-uninstall.1.html

@@ -0,0 +1,126 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <title>git-lfs-uninstall(1) - Remove 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-uninstall(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-uninstall(1)</li>
+  </ol>
+
+  
+
+<h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-uninstall</code> - <span class="man-whatis">Remove Git LFS configuration</span>
+</p>
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs uninstall</code></p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Perform the following actions to remove the Git LFS configuration:</p>
+
+<ul>
+  <li>Remove the "lfs" clean and smudge filters from the global Git config.</li>
+  <li>Uninstall the Git LFS pre-push hook if run from inside a Git repository.</li>
+</ul>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<dl>
+<dt>--local</dt>
+<dd>  Removes the "lfs" smudge and clean filters from the local repository's git
+  config, instead of the global git config (~/.gitconfig).</dd>
+<dt>--worktree</dt>
+<dd>  Removes the "lfs" smudge and clean filters from 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>--system</dt>
+<dd>  Removes the "lfs" smudge and clean filters from the system git config,
+  instead of the global git config (~/.gitconfig).</dd>
+<dt>--skip-repo</dt>
+<dd>  Skips cleanup of the local repo; use if you want to uninstall the global lfs
+  filters but not make changes to the current repo.</dd>
+</dl>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><a class="man-ref" href="git-lfs-install.1.html">git-lfs-install<span class="s">(1)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/git-worktree">git-worktree<span class="s">(1)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-uninstall(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-unlock.1.html

@@ -0,0 +1,120 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <title>git-lfs-unlock(1) - Remove &quot;locked&quot; setting for a file 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-unlock(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-unlock(1)</li>
+  </ol>
+
+  
+
+<h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-unlock</code> - <span class="man-whatis">Remove "locked" setting for a file on the Git LFS server</span>
+</p>
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs unlock</code> <a href="#OPTIONS" title="OPTIONS" data-bare-link="true">OPTIONS</a> <var>path</var></p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Removes the given file path as "locked" on the Git LFS server. Files must exist
+and have a clean git status before they can be unlocked. The <code>--force</code> flag will
+skip these checks.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<dl>
+<dt>
+<code>-r</code> <var>name</var> <code>--remote=</code><var>name</var>
+</dt>
+<dd>Specify the Git LFS server to use. Ignored if the <code>lfs.url</code> config key is set.</dd>
+<dt>
+<code>-f</code> <code>--force</code>
+</dt>
+<dd>Tells the server to remove the lock, even if it's owned by another user.</dd>
+<dt>
+<code>-i &lt;id&gt;</code> <code>--id=&lt;id&gt;</code>
+</dt>
+<dd>Specifies a lock by its ID instead of path.</dd>
+<dt><code>--json</code></dt>
+<dd>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.</dd>
+</dl>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><a class="man-ref" href="git-lfs-lock.1.html">git-lfs-lock<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-locks.1.html">git-lfs-locks<span class="s">(1)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-unlock(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-untrack.1.html

@@ -0,0 +1,108 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <title>git-lfs-untrack(1) - Remove Git LFS paths from Git Attributes</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-untrack(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-untrack(1)</li>
+  </ol>
+
+  
+
+<h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-untrack</code> - <span class="man-whatis">Remove Git LFS paths from Git Attributes</span>
+</p>
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs untrack</code> <var>path</var>...</p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Stop tracking the given path(s) through Git LFS.  The <var>path</var> argument
+can be a glob pattern or a file path.</p>
+
+<h2 id="EXAMPLES">EXAMPLES</h2>
+
+<dl>
+<dt>Configure Git LFS to stop tracking GIF files:
+
+    <p><code>git lfs untrack "*.gif"</code></p>
+</dt>
+<dd></dd>
+</dl>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p><a class="man-ref" href="git-lfs-track.1.html">git-lfs-track<span class="s">(1)</span></a>, <a class="man-ref" href="git-lfs-install.1.html">git-lfs-install<span class="s">(1)</span></a>, <a class="man-ref" href="https://git-scm.com/docs/gitattributes">gitattributes<span class="s">(5)</span></a>.</p>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-untrack(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs-update.1.html

@@ -0,0 +1,122 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <title>git-lfs-update(1) - Update Git hooks</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-update(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs-update(1)</li>
+  </ol>
+
+  
+
+<h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs-update</code> - <span class="man-whatis">Update Git hooks</span>
+</p>
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<table>
+  <tbody>
+    <tr>
+      <td>
+<code>git lfs update</code> [--manual</td>
+      <td>--force]</td>
+    </tr>
+  </tbody>
+</table>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Updates the Git hooks used by Git LFS. Silently upgrades known hook contents.
+If you have your own custom hooks you may need to use one of the extended
+options below.</p>
+
+<h2 id="OPTIONS">OPTIONS</h2>
+
+<ul>
+  <li>
+    <p><code>--manual</code> <code>-m</code>
+  Print instructions for manually updating your hooks to include git-lfs
+  functionality. Use this option if <code>git lfs update</code> fails because of existing
+  hooks and you want to retain their functionality.</p>
+  </li>
+  <li>
+    <p><code>--force</code> <code>-f</code>
+  Forcibly overwrite any existing hooks with git-lfs hooks. Use this option
+  if <code>git lfs update</code> fails because of existing hooks but you don't care
+  about their current contents.</p>
+  </li>
+</ul>
+
+<h2 id="SEE-ALSO">SEE ALSO</h2>
+
+<p>Part of the <a class="man-ref" href="git-lfs.1.html">git-lfs<span class="s">(1)</span></a> suite.</p>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs-update(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/html/git-lfs.1.html

@@ -0,0 +1,220 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <meta http-equiv='content-type' content='text/html;charset=utf8'>
+  <meta name='generator' content='Ronn-NG/v0.9.1 (http://github.com/apjanke/ronn-ng/tree/0.9.1)'>
+  <title>git-lfs(1) - Work with large files in Git repositories</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="#EXAMPLES">EXAMPLES</a>
+  </div>
+
+  <ol class='man-decor man-head man head'>
+    <li class='tl'>git-lfs(1)</li>
+    <li class='tc'></li>
+    <li class='tr'>git-lfs(1)</li>
+  </ol>
+
+  
+
+<h2 id="NAME">NAME</h2>
+<p class="man-name">
+  <code>git-lfs</code> - <span class="man-whatis">Work with large files in Git repositories</span>
+</p>
+<h2 id="SYNOPSIS">SYNOPSIS</h2>
+
+<p><code>git lfs</code> <var>command</var> [<var>args</var>]</p>
+
+<h2 id="DESCRIPTION">DESCRIPTION</h2>
+
+<p>Git LFS is a system for managing and versioning large files in
+association with a Git repository.  Instead of storing the large files
+within the Git repository as blobs, Git LFS stores special "pointer
+files" in the repository, while storing the actual file contents on a
+Git LFS server.  The contents of the large file are downloaded
+automatically when needed, for example when a Git branch containing
+the large file is checked out.</p>
+
+<p>Git LFS works by using a "smudge" filter to look up the large file
+contents based on the pointer file, and a "clean" filter to create a
+new version of the pointer file when the large file's contents change.
+It also uses a <code>pre-push</code> hook to upload the large file contents to
+the Git LFS server whenever a commit containing a new large file
+version is about to be pushed to the corresponding Git server.</p>
+
+<h2 id="COMMANDS">COMMANDS</h2>
+
+<p>Like Git, Git LFS commands are separated into high level ("porcelain")
+commands and low level ("plumbing") commands.</p>
+
+<h3 id="High-level-porcelain-commands">High level porcelain commands</h3>
+
+<dl>
+<dt><a class="man-ref" href="git-lfs-checkout.1.html">git-lfs-checkout<span class="s">(1)</span></a></dt>
+<dd>  Populate working copy with real content from Git LFS files.</dd>
+<dt><a class="man-ref" href="git-lfs-dedup.1.html">git-lfs-dedup<span class="s">(1)</span></a></dt>
+<dd>  De-duplicate Git LFS files.</dd>
+<dt><a class="man-ref" href="git-lfs-env.1.html">git-lfs-env<span class="s">(1)</span></a></dt>
+<dd>  Display the Git LFS environment.</dd>
+<dt><a class="man-ref" href="git-lfs-ext.1.html">git-lfs-ext<span class="s">(1)</span></a></dt>
+<dd>  Display Git LFS extension details.</dd>
+<dt><a class="man-ref" href="git-lfs-fetch.1.html">git-lfs-fetch<span class="s">(1)</span></a></dt>
+<dd>  Download Git LFS files from a remote.</dd>
+<dt><a class="man-ref" href="git-lfs-fsck.1.html">git-lfs-fsck<span class="s">(1)</span></a></dt>
+<dd>  Check Git LFS files for consistency.</dd>
+<dt><a class="man-ref" href="git-lfs-install.1.html">git-lfs-install<span class="s">(1)</span></a></dt>
+<dd>  Install Git LFS configuration.</dd>
+<dt><a class="man-ref" href="git-lfs-lock.1.html">git-lfs-lock<span class="s">(1)</span></a></dt>
+<dd>  Set a file as "locked" on the Git LFS server.</dd>
+<dt><a class="man-ref" href="git-lfs-locks.1.html">git-lfs-locks<span class="s">(1)</span></a></dt>
+<dd>  List currently "locked" files from the Git LFS server.</dd>
+<dt><a class="man-ref" href="git-lfs-logs.1.html">git-lfs-logs<span class="s">(1)</span></a></dt>
+<dd>  Show errors from the Git LFS command.</dd>
+<dt><a class="man-ref" href="git-lfs-ls-files.1.html">git-lfs-ls-files<span class="s">(1)</span></a></dt>
+<dd>  Show information about Git LFS files in the index and working tree.</dd>
+<dt><a class="man-ref" href="git-lfs-migrate.1.html">git-lfs-migrate<span class="s">(1)</span></a></dt>
+<dd>  Migrate history to or from Git LFS</dd>
+<dt><a class="man-ref" href="git-lfs-prune.1.html">git-lfs-prune<span class="s">(1)</span></a></dt>
+<dd>  Delete old Git LFS files from local storage</dd>
+<dt><a class="man-ref" href="git-lfs-pull.1.html">git-lfs-pull<span class="s">(1)</span></a></dt>
+<dd>  Fetch Git LFS changes from the remote &amp; checkout any required working tree
+  files.</dd>
+<dt><a class="man-ref" href="git-lfs-push.1.html">git-lfs-push<span class="s">(1)</span></a></dt>
+<dd>  Push queued large files to the Git LFS endpoint.</dd>
+<dt><a class="man-ref" href="git-lfs-status.1.html">git-lfs-status<span class="s">(1)</span></a></dt>
+<dd>  Show the status of Git LFS files in the working tree.</dd>
+<dt><a class="man-ref" href="git-lfs-track.1.html">git-lfs-track<span class="s">(1)</span></a></dt>
+<dd>  View or add Git LFS paths to Git attributes.</dd>
+<dt><a class="man-ref" href="git-lfs-uninstall.1.html">git-lfs-uninstall<span class="s">(1)</span></a></dt>
+<dd>  Uninstall Git LFS by removing hooks and smudge/clean filter configuration.</dd>
+<dt><a class="man-ref" href="git-lfs-unlock.1.html">git-lfs-unlock<span class="s">(1)</span></a></dt>
+<dd>  Remove "locked" setting for a file on the Git LFS server.</dd>
+<dt><a class="man-ref" href="git-lfs-untrack.1.html">git-lfs-untrack<span class="s">(1)</span></a></dt>
+<dd>  Remove Git LFS paths from Git Attributes.</dd>
+<dt><a class="man-ref" href="git-lfs-update.1.html">git-lfs-update<span class="s">(1)</span></a></dt>
+<dd>  Update Git hooks for the current Git repository.</dd>
+<dt><span class="man-ref">git-lfs-version<span class="s">(1)</span></span></dt>
+<dd>  Report the version number.</dd>
+</dl>
+
+<h3 id="Low-level-plumbing-commands">Low level plumbing commands</h3>
+
+<dl>
+<dt><a class="man-ref" href="git-lfs-clean.1.html">git-lfs-clean<span class="s">(1)</span></a></dt>
+<dd>  Git clean filter that converts large files to pointers.</dd>
+<dt><a class="man-ref" href="git-lfs-filter-process.1.html">git-lfs-filter-process<span class="s">(1)</span></a></dt>
+<dd>  Git process filter that converts between large files and pointers.</dd>
+<dt><a class="man-ref" href="git-lfs-merge-driver.1.html">git-lfs-merge-driver<span class="s">(1)</span></a></dt>
+<dd>  Merge text-based LFS files</dd>
+<dt><a class="man-ref" href="git-lfs-pointer.1.html">git-lfs-pointer<span class="s">(1)</span></a></dt>
+<dd>  Build and compare pointers.</dd>
+<dt><a class="man-ref" href="git-lfs-post-checkout.1.html">git-lfs-post-checkout<span class="s">(1)</span></a></dt>
+<dd>  Git post-checkout hook implementation.</dd>
+<dt><a class="man-ref" href="git-lfs-post-commit.1.html">git-lfs-post-commit<span class="s">(1)</span></a></dt>
+<dd>  Git post-commit hook implementation.</dd>
+<dt><a class="man-ref" href="git-lfs-post-merge.1.html">git-lfs-post-merge<span class="s">(1)</span></a></dt>
+<dd>  Git post-merge hook implementation.</dd>
+<dt><a class="man-ref" href="git-lfs-pre-push.1.html">git-lfs-pre-push<span class="s">(1)</span></a></dt>
+<dd>  Git pre-push hook implementation.</dd>
+<dt><a class="man-ref" href="git-lfs-smudge.1.html">git-lfs-smudge<span class="s">(1)</span></a></dt>
+<dd>  Git smudge filter that converts pointer in blobs to the actual content.</dd>
+<dt><a class="man-ref" href="git-lfs-standalone-file.1.html">git-lfs-standalone-file<span class="s">(1)</span></a></dt>
+<dd>  Git LFS standalone transfer adapter for file URLs (local paths).</dd>
+</dl>
+
+<h2 id="EXAMPLES">EXAMPLES</h2>
+
+<p>To get started with Git LFS, the following commands can be used.</p>
+
+<ol>
+  <li>
+    <p>Setup Git LFS on your system. You only have to do this once per
+repository per machine:</p>
+
+    <pre><code>git lfs install
+</code></pre>
+  </li>
+  <li>
+    <p>Choose the type of files you want to track, for examples all <code>ISO</code>
+images, with <a class="man-ref" href="git-lfs-track.1.html">git-lfs-track<span class="s">(1)</span></a>:</p>
+
+    <pre><code>git lfs track "*.iso"
+</code></pre>
+  </li>
+  <li>
+    <p>The above stores this information in <a class="man-ref" href="https://git-scm.com/docs/gitattributes">gitattributes<span class="s">(5)</span></a> files, so
+that file needs to be added to the repository:</p>
+
+    <pre><code>git add .gitattributes
+</code></pre>
+  </li>
+  <li>
+    <p>Commit, push and work with the files normally:</p>
+
+    <pre><code>git add file.iso
+git commit -m "Add disk image"
+git push
+</code></pre>
+  </li>
+</ol>
+
+  <ol class='man-decor man-foot man foot'>
+    <li class='tl'></li>
+    <li class='tc'>May 2022</li>
+    <li class='tr'>git-lfs(1)</li>
+  </ol>
+
+  </div>
+</body>
+</html>

git-lfs-3.2.0/man/man1/git-lfs-checkout.1

@@ -0,0 +1,50 @@
+.\" generated with Ronn-NG/v0.9.1
+.\" http://github.com/apjanke/ronn-ng/tree/0.9.1
+.TH "GIT\-LFS\-CHECKOUT" "1" "May 2022" ""
+.SH "NAME"
+\fBgit\-lfs\-checkout\fR \- Update working copy with file content if available
+.SH "SYNOPSIS"
+\fBgit lfs checkout\fR [\fIglob\-pattern\fR\|\.\|\.\|\.]
+.br
+\fBgit lfs checkout\fR \-\-to \fIfile\fR {\-\-base|\-\-ours|\-\-theirs} \fIconflict\-obj\-path\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
+One or more \fIglob\-pattern\fRs may be provided as arguments to restrict the set of files that are updated\. Glob patterns are matched as per the format described in gitignore(5)\.
+.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 a conflicting Git LFS object into a separate file (which can be outside of the work tree)\. This can make using diff tools to inspect and resolve merges easier\. A single Git LFS object\'s file path must be provided in \fIconflict\-obj\-path\fR\.
+.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"
+.TP
+Checkout all files that are missing or placeholders:
+
+.P
+\fB$ git lfs checkout\fR
+.TP
+Checkout a specific couple of files:
+
+.P
+\fB$ git lfs checkout path/to/file1\.png path/to\.file2\.png\fR
+.TP
+Checkout a path with a merge conflict into separate files:
+
+.P
+``` # Attempt merge with a branch that has a merge conflict $ git merge conflicting\-branch CONFLICT (content): Merge conflict in path/to/conflicting/file\.dat$ git lfs checkout ours\.dat \-\-ours path/to/conflicting/file\.dat $ git lfs checkout theirs\.dat \-\-theirs path/to/conflicting/file\.dat# then resolve conflict (e\.g\., by choosing one version over # the other, or creating a new version)$ rm ours\.dat theirs\.dat $ git add path/to/conflicting/file\.dat $ git merge \-\-continue ```
+.SH "SEE ALSO"
+git\-lfs\-fetch(1), git\-lfs\-pull(1), gitignore(5)\.
+.P
+Part of the git\-lfs(1) suite\.

git-lfs-3.2.0/man/man1/git-lfs-clean.1

@@ -0,0 +1,17 @@
+.\" generated with Ronn-NG/v0.9.1
+.\" http://github.com/apjanke/ronn-ng/tree/0.9.1
+.TH "GIT\-LFS\-CLEAN" "1" "May 2022" ""
+.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\.

git-lfs-3.2.0/man/man1/git-lfs-clone.1

@@ -0,0 +1,34 @@
+.\" generated with Ronn-NG/v0.9.1
+.\" http://github.com/apjanke/ronn-ng/tree/0.9.1
+.TH "GIT\-LFS\-CLONE" "1" "May 2022" ""
+.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 your Git configuration or in a \fB\.lfsconfig\fR file, you may set either or both of \fBlfs\.fetchinclude\fR and \fBlfs\.fetchexclude\fR to comma\-separated lists of paths\. If \fBlfs\.fetchinclude\fR is defined, Git LFS objects will only be fetched if their path matches one in that list, and if \fBlfs\.fetchexclude\fR is defined, Git LFS objects will only be fetched if their path does not match one in that list\. Paths are matched using wildcard matching as per gitignore(5)\.
+.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 "SEE ALSO"
+git\-clone(1), git\-lfs\-pull(1), gitignore(5)\.
+.P
+Part of the git\-lfs(1) suite\.

git-lfs-3.2.0/man/man1/git-lfs-dedup.1

@@ -0,0 +1,15 @@
+.\" generated with Ronn-NG/v0.9.1
+.\" http://github.com/apjanke/ronn-ng/tree/0.9.1
+.TH "GIT\-LFS\-DEDUP" "1" "May 2022" ""
+.SH "NAME"
+\fBgit\-lfs\-dedup\fR \- Deduplicate Git LFS files
+.SH "SYNOPSIS"
+\fBgit lfs dedup\fR
+.SH "DESCRIPTION"
+Deduplicates storage by re\-creating working tree files as clones of the files in the Git LFS storage directory using the operating system\'s copy\-on\-write file creation functionality\.
+.P
+If the operating system or file system don\'t support copy\-on\-write file creation, this command exits unsuccessfully\.
+.P
+This command will also exit without success if any Git LFS extensions are configured, as these will typically be used to alter the file contents before they are written to the Git LFS storage directory, and therefore the working tree files should not be copy\-on\-write clones of the LFS object files\.
+.SH "SEE ALSO"
+Part of the git\-lfs(1) suite\.

git-lfs-3.2.0/man/man1/git-lfs-env.1

@@ -0,0 +1,11 @@
+.\" generated with Ronn-NG/v0.9.1
+.\" http://github.com/apjanke/ronn-ng/tree/0.9.1
+.TH "GIT\-LFS\-ENV" "1" "May 2022" ""
+.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\.

git-lfs-3.2.0/man/man1/git-lfs-ext.1

@@ -0,0 +1,21 @@
+.\" generated with Ronn-NG/v0.9.1
+.\" http://github.com/apjanke/ronn-ng/tree/0.9.1
+.TH "GIT\-LFS\-EXT" "1" "May 2022" ""
+.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 "\[ci]" 4
+List details for all extensions
+.IP
+\fBgit lfs ext\fR \fBgit lfs ext list\fR
+.IP "\[ci]" 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\.

git-lfs-3.2.0/man/man1/git-lfs-fetch.1

@@ -0,0 +1,100 @@
+.\" generated with Ronn-NG/v0.9.1
+.\" http://github.com/apjanke/ronn-ng/tree/0.9.1
+.TH "GIT\-LFS\-FETCH" "1" "May 2022" ""
+.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 your Git configuration or in a \fB\.lfsconfig\fR file, you may set either or both of \fBlfs\.fetchinclude\fR and \fBlfs\.fetchexclude\fR to comma\-separated lists of paths\. If \fBlfs\.fetchinclude\fR is defined, Git LFS objects will only be fetched if their path matches one in that list, and if \fBlfs\.fetchexclude\fR is defined, Git LFS objects will only be fetched if their path does not match one in that list\. Paths are matched using wildcard matching as per gitignore(5)\.
+.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 "\[ci]" 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 "\[ci]" 4
+\fBgit config lfs\.fetchinclude "*\.jpg,*\.png,*\.tga"\fR
+.IP
+Only fetch JPG/PNG/TGA files, wherever they are in the repository
+.IP "\[ci]" 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 "\[ci]" 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 "\[ci]" 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 "\[ci]" 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 "\[ci]" 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 "\[ci]" 4
+\fBlfs\.fetchrecentalways\fR Always operate as if \-\-recent was provided on the command line\.
+.IP "" 0
+.SH "EXAMPLES"
+.IP "\[ci]" 4
+Fetch the LFS objects for the current ref from default remote
+.IP
+\fBgit lfs fetch\fR
+.IP "\[ci]" 4
+Fetch the LFS objects for the current ref AND recent changes from default remote
+.IP
+\fBgit lfs fetch \-\-recent\fR
+.IP "\[ci]" 4
+Fetch the LFS objects for the current ref from a secondary remote \'upstream\'
+.IP
+\fBgit lfs fetch upstream\fR
+.IP "\[ci]" 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 "\[ci]" 4
+Fetch the LFS objects for a branch from origin
+.IP
+\fBgit lfs fetch origin mybranch\fR
+.IP "\[ci]" 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), gitconfig(5)\.
+.P
+Part of the git\-lfs(1) suite\.

git-lfs-3.2.0/man/man1/git-lfs-filter-process.1

@@ -0,0 +1,27 @@
+.\" generated with Ronn-NG/v0.9.1
+.\" http://github.com/apjanke/ronn-ng/tree/0.9.1
+.TH "GIT\-LFS\-FILTER\-PROCESS" "1" "May 2022" ""
+.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
+In your Git configuration or in a \fB\.lfsconfig\fR file, you may set either or both of \fBlfs\.fetchinclude\fR and \fBlfs\.fetchexclude\fR to comma\-separated lists of paths\. If \fBlfs\.fetchinclude\fR is defined, Git LFS pointer files will only be replaced with the contents of the corresponding Git LFS object file if their path matches one in that list, and if \fBlfs\.fetchexclude\fR is defined, Git LFS pointer files will only be replaced with the contents of the corresponding Git LFS object file if their path does not match one in that list\. Paths are matched using wildcard matching as per gitignore(5)\. Git LFS pointer files that are not replaced with the contents of their corresponding object files are simply copied to standard output without change\.
+.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), gitignore(5)\.
+.P
+Part of the git\-lfs(1) suite\.

git-lfs-3.2.0/man/man1/git-lfs-fsck.1

@@ -0,0 +1,28 @@
+.\" generated with Ronn-NG/v0.9.1
+.\" http://github.com/apjanke/ronn-ng/tree/0.9.1
+.TH "GIT\-LFS\-FSCK" "1" "May 2022" ""
+.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\.
+.P
+In your Git configuration or in a \fB\.lfsconfig\fR file, you may set \fBlfs\.fetchexclude\fR to a comma\-separated list of paths\. If \fBlfs\.fetchexclude\fR is defined, then any Git LFS files whose paths match one in that list will not be checked for consistency\. Paths are matched using wildcard matching as per gitignore(5)\.
+.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), gitignore(5)\.
+.P
+Part of the git\-lfs(1) suite\.