git-stripspace(1) [mojave man page]
GIT-STRIPSPACE(1) Git Manual GIT-STRIPSPACE(1) NAME
git-stripspace - Remove unnecessary whitespace SYNOPSIS
git stripspace [-s | --strip-comments] git stripspace [-c | --comment-lines] DESCRIPTION
Read text, such as commit messages, notes, tags and branch descriptions, from the standard input and clean it in the manner used by Git. With no arguments, this will: o remove trailing whitespace from all lines o collapse multiple consecutive empty lines into one empty line o remove empty lines from the beginning and end of the input o add a missing to the last line if necessary. In the case where the input consists entirely of whitespace characters, no output will be produced. NOTE: This is intended for cleaning metadata, prefer the --whitespace=fix mode of git-apply(1) for correcting whitespace of patches or files in the repository. OPTIONS
-s, --strip-comments Skip and remove all lines starting with comment character (default #). -c, --comment-lines Prepend comment character and blank to each line. Lines will automatically be terminated with a newline. On empty lines, only the comment character will be prepended. EXAMPLES
Given the following noisy input with $ indicating the end of a line: |A brief introduction $ | $ |$ |A new paragraph$ |# with a commented-out line $ |explaining lots of stuff.$ |$ |# An old paragraph, also commented-out. $ | $ |The end.$ | $ Use git stripspace with no arguments to obtain: |A brief introduction$ |$ |A new paragraph$ |# with a commented-out line$ |explaining lots of stuff.$ |$ |# An old paragraph, also commented-out.$ |$ |The end.$ Use git stripspace --strip-comments to obtain: |A brief introduction$ |$ |A new paragraph$ |explaining lots of stuff.$ |$ |The end.$ GIT
Part of the git(1) suite Git 2.17.1 10/05/2018 GIT-STRIPSPACE(1)
Check Out this Related Man Page
GIT-PRUNE(1) Git Manual GIT-PRUNE(1) NAME
git-prune - Prune all unreachable objects from the object database SYNOPSIS
git prune [-n] [-v] [--progress] [--expire <time>] [--] [<head>...] DESCRIPTION
Note In most cases, users should run git gc, which calls git prune. See the section "NOTES", below. This runs git fsck --unreachable using all the refs available in refs/, optionally with additional set of objects specified on the command line, and prunes all unpacked objects unreachable from any of these head objects from the object database. In addition, it prunes the unpacked objects that are also found in packs by running git prune-packed. It also removes entries from .git/shallow that are not reachable by any ref. Note that unreachable, packed objects will remain. If this is not desired, see git-repack(1). OPTIONS
-n, --dry-run Do not remove anything; just report what it would remove. -v, --verbose Report all removed objects. --progress Show progress. --expire <time> Only expire loose objects older than <time>. -- Do not interpret any more arguments as options. <head>... In addition to objects reachable from any of our references, keep objects reachable from listed <head>s. EXAMPLE
To prune objects not used by your repository or another that borrows from your repository via its .git/objects/info/alternates: $ git prune $(cd ../another && git rev-parse --all) NOTES
In most cases, users will not need to call git prune directly, but should instead call git gc, which handles pruning along with many other housekeeping tasks. For a description of which objects are considered for pruning, see git fsck's --unreachable option. SEE ALSO
git-fsck(1), git-gc(1), git-reflog(1) GIT
Part of the git(1) suite Git 2.17.1 10/05/2018 GIT-PRUNE(1)