Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

git-prune-packed(1) [xfree86 man page]

GIT-PRUNE-PACKED(1)						    Git Manual						       GIT-PRUNE-PACKED(1)

NAME
git-prune-packed - Remove extra objects that are already in pack files SYNOPSIS
git prune-packed [-n|--dry-run] [-q|--quiet] DESCRIPTION
This program searches the $GIT_OBJECT_DIRECTORY for all objects that currently exist in a pack file as well as the independent object directories. All such extra objects are removed. A pack is a collection of objects, individually compressed, with delta compression applied, stored in a single file, with an associated index file. Packs are used to reduce the load on mirror systems, backup engines, disk storage, etc. OPTIONS
-n, --dry-run Don't actually remove any objects, only show those that would have been removed. -q, --quiet Squelch the progress indicator. SEE ALSO
git-pack-objects(1) git-repack(1) GIT
Part of the git(1) suite Git 2.17.1 10/05/2018 GIT-PRUNE-PACKED(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)
Man Page

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

No xorg.conf or XF86Config

There is no xorg.conf file and no XF86Config file on a certain FreeBSD machine: # locate xorg.conf /usr/local/man/man5/xorg.conf.5.gz # locate XF86Config # Can someone let me know if that means that there is a bare bones set up possible only? xrandr works fine, but I am looking for ways to... (6 Replies)
Discussion started by: figaro
6 Replies

2. Shell Programming and Scripting

Can a script resize it's own mintty console?

I'm looking for finer granularity than the 20 ANSI escape sequence screen modes. What I'd like to do is have the terminal increase it's own height when I have to show the user a long menu. Platform is Cygwin 64 running over Win 7 Pro. Mike (4 Replies)
Discussion started by: Michael Stora
4 Replies

3. UNIX for Advanced & Expert Users

Shopt -s histappend

What is the point of this? Whenever I close my shell it appends to the history file without adding this. I have never seen it overwrite my history file. # When the shell exits, append to the history file instead of overwriting it shopt -s histappend (3 Replies)
Discussion started by: cokedude
3 Replies

4. Fedora

Fedora 30 and Slackware 14.2, how to obtain the same rendering?

Look this very good rendering on Slackware 14.2 in my opinion is near perfect. https://i.stack.imgur.com/q5trL.png Now look the same page on Fedora 30 https://i.stack.imgur.com/FBQv7.png In my opinion the fonts on Fedora are too small and difficult to read, I prefer the fat fonts of... (20 Replies)
Discussion started by: Linusolaradm1
20 Replies