NAME git-gc - Cleanup unnecessary files and optimize the local repository SYNOPSIS git gc [--aggressive ... rewrite the commit-graph file when git-gc (1) is run. When using git gcconsolidated into larger pack(s). See git-gc (1) and git-pack-objects ... expired objects instead of waiting for git-gc (1) to expire those objects laternext git gc invocation. See git-gc (1). -d After packing, if the newly created ... next git gc invocation (see git-gc (1)). Incompatible with -k . --cruft-expiration= Expire unrea…Prepare patches for e-mail submission. git-gc (1) Cleanup unnecessary files and optimizegit’s built-in housekeeping (see git-gc (1)). SECURITY The fetch and push protocolsoption. SEE ALSO git-fsck (1), git-gc (1), git-reflog (1) GIT Partdirectly by end users — instead, see git-gc (1). The "delete" subcommand deletes single entriesinvoked by git gc --auto (see git-gc (1)). It takes no parameter, and exitingrefs to operations such as git-gc (1). Storing multiple repositories as namespacesnoted in the "AGGRESSIVE" section in git-gc (1) the --aggressive option will finddeletes stale data. See git-gc (1) for more details on garbage collection in Gitcommands such as git gc (see git-gc (1)), git repack (see git-repackgc --prune=now (or if your git-gc is not new enough to support argumentsfetch (1), git-pack-refs (1), git-gc (1), git-checkout (1), gitglossary