You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Help text for git-lfs can be generated by simply typing git-lfs at a command prompt. Some of the resulting help text appears to have formatting left in it. For example, notice the dots and + characters in this exerpt:
Examples
--------
To get started with Git LFS, the following commands can be used.
. Setup Git LFS on your system. You only have to do this once per user
account:
+
git lfs install
. Choose the type of files you want to track, for examples all ISO
images, with git lfs track:
+
git lfs track "*.iso"
. The above stores this information in gitattributes(5) files, so that
file needs to be added to the repository:
+
git add .gitattributes
. Commit, push and work with the files normally:
+
The text was updated successfully, but these errors were encountered:
Hey, thanks for the report! This looks like something we should be able to improve, and I suspect there are some other formatting anomalies in our manual pages as well.
The code which converts our AsciiDoc manual page source files to text is in the docs/man/mangen.gofile, if anyone wants to take a look and try to craft a PR to address this issue.
In the meantime, I'll put this into our backlog as an improvement we'd like to make.
Help text for
git-lfs
can be generated by simply typinggit-lfs
at a command prompt. Some of the resulting help text appears to have formatting left in it. For example, notice the dots and + characters in this exerpt:The text was updated successfully, but these errors were encountered: